linux-kernel - Re: [PATCH/RFC] parport_pc: remove ancient, overeager quirk that disables EPP support on many chipsets

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 15 Sep 2011 15:35:31 -0500
From:	Jonathan Nieder <jrnieder@...il.com>
To:	Adam Baker <linux@...er-net.org.uk>
Cc:	Greg KH <greg@...ah.com>,
	Leopold Palomo-Avellaneda <leo@...xarxa.net>,
	linux-kernel@...r.kernel.org, linux-parport@...ts.infradead.org,
	Nicos Gollan <gollan@...ormatik.uni-kl.de>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Alexander Gordeev <lasaine@....cs.msu.su>
Subject: Re: [PATCH/RFC] parport_pc: remove ancient, overeager quirk that
 disables EPP support on many chipsets

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. :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/