LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Jean Delvare <khali@linux-fr.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
	Greg KH <greg@kroah.com>,
	andrea@suse.de, tim@cyberelk.net, philb@gnu.org
Subject: Re: [patch/rfc 2.6.20-git] parport reports physical devices
Date: Sat, 24 Feb 2007 13:49:40 -0800	[thread overview]
Message-ID: <200702241349.40906.david-b@pacbell.net> (raw)
In-Reply-To: <20070220221043.ead0b744.khali@linux-fr.org>

On Tuesday 20 February 2007 1:10 pm, Jean Delvare wrote:
> 
> > There are probably good reasons (== deep hardware braindamage on older
> > systems that are now hard to find) for the strange init sequencing in
> > that code, but I can't see why they should prevent splitting out
> > 
> > 	(a) device discovery via probing, PNP, or whatever; from
> > 
> > 	(b) the driver itself, getting handed a device node that's
> > 	    pre-configured with the resources reported by discovery.
> > 
> > Maybe the maintainers of the parport stack will have comments.  Though
> > the info in MAINTAINERS seems dated, if not obsolete.
> 
> Phil Blundell and Tim Waugh did not reply to me last time I sent a
> parport cleanup patch to them. I suspect they are indeed no longer
> maintaining parport in practice.

Neither of them seem to have acked patches in drivers/parport for some
time either, much less signed off on them.  And that webpage lists the
latest patches (from Tim) ... for 2.5.6-pre2!!  For the moment I've got
the appended patch in my set of parport patches.  Unless one of the
folk listed as maintainers (cc'd) squawks appropriately, I'll send this
along with the next batch of patches. 

- Dave


The writing on the wall seem to be that the parport stack is orphaned,
rather than maintained...

Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>

Index: g26/MAINTAINERS
===================================================================
--- g26.orig/MAINTAINERS	2007-02-20 22:17:27.000000000 -0800
+++ g26/MAINTAINERS	2007-02-20 22:22:57.000000000 -0800
@@ -2553,16 +2553,8 @@ L:	i2c@lm-sensors.org
 S:	Maintained
 
 PARALLEL PORT SUPPORT
-P:	Phil Blundell
-M:	philb@gnu.org
-P:	Tim Waugh
-M:	tim@cyberelk.net
-P:	David Campbell
-P:	Andrea Arcangeli
-M:	andrea@suse.de
 L:	linux-parport@lists.infradead.org
-W:	http://people.redhat.com/twaugh/parport/
-S:	Maintained
+S:	Orphan
 
 PARIDE DRIVERS FOR PARALLEL PORT IDE DEVICES
 P:	Tim Waugh

      parent reply	other threads:[~2007-02-24 21:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-19  5:08 David Brownell
2007-02-19  5:28 ` Randy Dunlap
2007-02-19  5:52   ` David Brownell
2007-02-19 14:18 ` Jean Delvare
2007-02-19 16:40   ` David Brownell
2007-02-20 21:10     ` Jean Delvare
2007-02-24 21:40       ` David Brownell
2007-02-24 21:49       ` David Brownell [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200702241349.40906.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=andrea@suse.de \
    --cc=greg@kroah.com \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philb@gnu.org \
    --cc=tim@cyberelk.net \
    --subject='Re: [patch/rfc 2.6.20-git] parport reports physical devices' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).