linux-kernel - Re: [GIT]: Networking

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:	Wed, 3 Sep 2008 16:20:43 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	David Miller <davem@...emloft.net>
cc:	akpm@...ux-foundation.org, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT]: Networking

On Wed, 3 Sep 2008, David Miller wrote:
> 
> 4) Several iwlwifi fixes:

Are these really regressions?

And if they aren't, why are they here and now?

Are people really so _stupid_ that they think that no fixes ever cause new 
regressions, so that they think that because they are "fixes" they are 
safe?

Please, guys. I complained once about this already. What's so hard to 
understand?

Do development _separately_. Push new development during the merge window. 
Don't do it later. And don't think that just because it's a 'fix', it 
should go upstream asap.

What's so hard to understand about this?

I'll pull this YET AGAIN, but I'm getting really fed up with telling the 
same people the same thing over and over again. It looks like the iwlwifi 
people don't understand what "merge window" means, and thinks that any 
random fix for any random issue should always just be pushed up.

		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/