linux-kernel - Re: [kvm-devel] [PATCH 045/104] KVM: Fix defined but not used warning in drivers/kvm/vmx.c

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]

Message-ID: <46EEBAFF.2040505@qumranet.com>
Date:	Mon, 17 Sep 2007 19:35:59 +0200
From:	Avi Kivity <avi@...ranet.com>
To:	David Miller <davem@...emloft.net>
CC:	kvm-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [kvm-devel] [PATCH 045/104] KVM: Fix defined but not used warning
 in drivers/kvm/vmx.c

David Miller wrote:
> You've got to be kidding me.
>
> 104 patches is way over the top, post them in smaller chunks
> please instead of killing vger.kernel.org as it has to crunch
> out every single one of these 104 patches to several thousand
> recipients.
>
>   

I can understand the load on the humans (and will split into several
rounds in the future), but why is vger.kernel.org so badly affected? 
Shouldn't the mta throttle itself instead of dying?

Just curious.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

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