From: Jonathan Nieder <jrnieder@gmail.com>
To: Adam Baker <linux@baker-net.org.uk>
Cc: Greg KH <greg@kroah.com>,
Leopold Palomo-Avellaneda <leo@alaxarxa.net>,
linux-kernel@vger.kernel.org, linux-parport@lists.infradead.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 15:35:31 -0500 [thread overview]
Message-ID: <20110915203530.GA31345@elie> (raw)
In-Reply-To: <201109152123.07678.linux@baker-net.org.uk>
Adam Baker wrote:
> The code has sat around for a long time because when I first posted the patch
> I got no feedback to indicate if anyone else was suffering from the bug and if
> anyone else had hardware that exhibited the bug it was supposed to fix so I
> didn't want to pursue submitting it. Over the years I have seen occasional
> reports of users suffering from the problem but I no longer have any EPP
> hardware to test it on.
>
> That's why I posted the mail that said if someone else can verify the patch is
> still useful I'm happy for it to be submitted with my signed off by on it
Makes sense. Thanks for explaining and thanks for your work, Adam.
Actually I think 3 years before a patch gets the attention it deserves
is not so bad --- it was mostly that the problem has been known since
1999 that bothered me. :)
next prev parent reply other threads:[~2011-09-15 20:35 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
2011-09-15 20:23 ` Adam Baker
2011-09-15 20:35 ` Jonathan Nieder [this message]
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=20110915203530.GA31345@elie \
--to=jrnieder@gmail.com \
--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