From: Jonathan Nieder <jrnieder@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Leopold Palomo-Avellaneda <leo@alaxarxa.net>,
linux-kernel@vger.kernel.org, Adam Baker <linux@baker-net.org.uk>,
linux-parport@lists.infradead.org, 630593@bugs.debian.org,
Nicos Gollan <gollan@informatik.uni-kl.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Alexander Gordeev <lasaine@lvk.cs.msu.su>
Subject: Re: [PATCH/RFC] parport_pc: remove ancient, overeager quirk that disables EPP support on many chipsets
Date: Thu, 15 Sep 2011 12:39:50 -0500 [thread overview]
Message-ID: <20110915173950.GA19450@elie> (raw)
In-Reply-To: <20110915133555.GB16636@kroah.com>
Hi,
Greg KH wrote:
> You can not add someone else's signed-off-by: line to a patch, please go
> re-read Documentation/SubmittingPatches as to why.
>
> And did Adam originally write this patch? Or did you? If Adam, please
> set the authorship information properly.
>From a quick Google search:
http://lists.infradead.org/pipermail/linux-parport/2008-March/000628.html
It looks like this one does have Adam Baker's sign-off (and it is sad
how long this patch seems to have sat without being submitted to
mainline).
I don't know who originally had the idea of removing that code. See
[1], [2], [3], and [4] for some early discussions.
The current "intel parport bug" test this patch removes seems to have
been introduced between 2.3.10pre5 and 2.3.10 (thanks to Dave Jones
for the git tree that makes such searches easy!). That means some
time around June or July, 1999. At the time, the parport maintainers
according to MAINTAINERS were Phil Blundell, Tim Waugh, David
Campbell, and Andrea Arcangeli. From the patch "[PATCH] parport is an
orphan", 2007-03-05, I infer that not all of them are still interested
in the driver and whoever _is_ interested is probably subscribed to
the (low-volume) linux-parport list.
I'd say, why not get this patch in linux-next or -mm somehow and see
if anyone screams? It would be _very_ useful to find an actual
instance of the "intel parport bug" so we could see what that code was
supposed to do and do it better.
Thanks,
Jonathan
[1] http://thread.gmane.org/gmane.linux.parport/322/focus=326
[2] http://thread.gmane.org/gmane.linux.parport/324/focus=327
[3] http://thread.gmane.org/gmane.linux.parport/806
[4] http://thread.gmane.org/gmane.linux.parport/925/focus=929
next prev parent reply other threads:[~2011-09-15 17:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 12:41 [PATCH/RFC] parport_pc: remove ancient, overeager quirk that disables EPP support on many chipsets Leopold Palomo-Avellaneda
2011-09-15 13:35 ` Greg KH
2011-09-15 17:39 ` Jonathan Nieder [this message]
2011-09-15 20:23 ` Adam Baker
2011-09-15 20:35 ` Jonathan Nieder
2011-09-16 10:09 ` Leopold Palomo-Avellaneda
2011-09-15 13:41 ` Bastien ROUCARIES
2011-09-15 13:44 ` Bastien ROUCARIES
2011-09-16 10:39 ` Leopold Palomo-Avellaneda
2011-09-15 19:43 ` Jonathan Nieder
-- strict thread matches above, loose matches on Subject: below --
2011-09-15 13:02 Leopold Palomo-Avellaneda
2011-09-15 9:33 Leopold Palomo-Avellaneda
2011-09-15 10:16 ` Greg KH
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=20110915173950.GA19450@elie \
--to=jrnieder@gmail.com \
--cc=630593@bugs.debian.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gollan@informatik.uni-kl.de \
--cc=greg@kroah.com \
--cc=lasaine@lvk.cs.msu.su \
--cc=leo@alaxarxa.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parport@lists.infradead.org \
--cc=linux@baker-net.org.uk \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox