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, 30 Aug 2007 13:02:35 -0600
From:	Matthew Wilcox <matthew@....cx>
To:	Jan Engelhardt <jengelh@...putergmbh.de>
Cc:	Denys Vlasenko <vda.linux@...glemail.com>,
	Arjan van de Ven <arjan@...radead.org>,
	Adrian Bunk <bunk@...nel.org>, Andrew Morton <akpm@...l.org>,
	linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
	hare@...e.de
Subject: Re: [PATCH] debloat aic7xxx and aic79xx drivers by deinlining

On Thu, Aug 30, 2007 at 08:43:24PM +0200, Jan Engelhardt wrote:
> On Aug 28 2007 20:55, Denys Vlasenko wrote:
> >> Fwiw I do like your debloat patch a lot; it's just only half the
> >> equation ... if you also do the namespace fixes, I bet the driver
> >> debloats even more...
> >
> >Yes, I know, and I am happy to do that too. I just don't know
> >whether patches will be accepted.
> >
> >Why this patch is not commented on by scsi people?
> >Am I sending patches to wrong people/lists?
> 
> Well, you can send it to Linus/Andrew, that will usually upset people and they
> start commenting on it. Or they don't, and everything is fine.
> (The "default y" approach so to speak ;-)

The problem is that we don't really have a maintainer for the aic7xyz
drivers any more.  Volunteers welcome.  NOT IT!

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ