linux-kernel - Re: [PATCH] Promise 'stex' driver

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] [day] [month] [year] [list]

Message-ID: <44C3DA2F.1090107@garzik.org>
Date:	Sun, 23 Jul 2006 16:21:03 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	hch <hch@...radead.org>, Jeff Garzik <jeff@...zik.org>,
	Jens Axboe <axboe@...e.de>,
	James Bottomley <James.Bottomley@...elEye.com>,
	Ed Lin <ed.lin@...mise.com>,
	"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	akpm <akpm@...l.org>, promise_linux <promise_linux@...mise.com>
Subject: Re: [PATCH] Promise 'stex' driver

hch wrote:
> On Thu, Jul 20, 2006 at 11:01:02PM -0400, Jeff Garzik wrote:
>> I think it's highly rude to presume that someone who has so-far been 
>> responsive, and responsible, will suddenly not be so.  That is not the 
>> way to encourage vendors to join the Linux process.
> 
> But it is like that in practice.  I know more than enough examples where
> there is no more incentive to fix things up once it's in, heck I'm guilty
> of that myself.  It has to do with beeing lazy and not wanting to change code
> anymore once it has settled.

I agree -- but in this case we have direct evidence to the contrary.

I'll stay on their back, if nothing else...

	Jeff



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