linux-kernel - Re: [PATCH 0/8] floppy: cleanup patches

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]

Message-ID: <DC0C730083854824867BF062E17E7FAA@hugo>
Date:	Sun, 13 Jun 2010 19:23:28 +0200
From:	"Thomas Meyer" <thomas@...3r.de>
To:	"Stephen Hemminger" <shemminger@...tta.com>
Cc:	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/8] floppy: cleanup patches

----- Original Message ----- 
From: "Stephen Hemminger" <shemminger@...tta.com>
> On Thu, 10 Jun 2010 08:43:32 +0200
> Thomas Meyer <thomas@...3r.de> wrote:
> 
>> Am Mittwoch, den 09.06.2010, 11:34 -0700 schrieb Stephen Hemminger:
>> > When going through floppy driver addressing some of the timing
>> > bugs, I also saw these leftover things that ought to be cleaned up.
>> >   
>> 
>> With your patches applied on top of 2.6.34 I still get this timeout
>> while resuming from ram:
> 
> Not clear, did the problem occur before my patches?

Yes, the timeout occured before your patches, i.e. plain 2.6.34.

> The posted set
> of patches should not change visible functionalty or fix any observable
> bug. Floppy driver would be bug for bug the same.

I guess, it's okay then.

kind regards
thomas


--
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/