linux-kernel - Re: [GIT PULL][RESEND] KVM cpu hotplug fixes

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:	Fri, 1 Jun 2007 08:22:33 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Avi Kivity <avi@...ranet.com>
cc:	kvm-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL][RESEND] KVM cpu hotplug fixes

On Fri, 1 Jun 2007, Avi Kivity wrote:
> 
> Please pull from the repository and branch

No. Not after -rc1. Not for something that changes core code and isn't a 
core feature, and wasn't a regression.

> The core issue is that we need a notification [...]

No. The core issue here is that people need to understand that if you miss 
the merge window, and it's new development, YOU DAMN WELL WAIT FOR THE 
NEXT ONE.

Don't send me pull requests like this. And absolutely do NOT send them as 
resends. I just  get grumpy.

If all the added code had been KVM-only, I might not care. But when the 
bulk of the code touches core files, you had better explain why this is so 
important that it cannot wait for the next merge window. 

			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/