linux-kernel - Re: [GIT PULL] SCSI fixes for 2.6.32-rc3

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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 8 Oct 2009 07:39:34 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	James Bottomley <James.Bottomley@...e.de>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-scsi <linux-scsi@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] SCSI fixes for 2.6.32-rc3

On Thu, 8 Oct 2009, James Bottomley wrote:
> 
> So what do you want to do about this? 

I'm taking it (and the parisc one I was also unhappy with), but I'm a bit 
grumpy as usual. The parisc pull came totally outside the merge window, 
and the SCSI fix pull is technically perfectly fine, but what makes me 
grumpy is that I get the strong feeling that people aren't even _trying_ 
to hit the merge window with new drivers, because they decide that they 
instead can just push them any time.

So I don't think I necessarily want to change the "new driver" policy per 
se, but I want people to see the merge window as the _primary_ time you 
get any new code in. The "yes, we'll take new drivers" thing should be the 
exception rather than the rule. It doesn't seem to be an exception.

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