linux-kernel - Re: [PATCH 0/8] AMD opteron mm config numa etc

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] [day] [month] [year] [list]

Message-ID: <20080220103831.GH3881@elte.hu>
Date:	Wed, 20 Feb 2008 11:38:31 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Greg KH <greg@...ah.com>, Yinghai Lu <Yinghai.Lu@....COM>,
	Jeff Garzik <jeff@...zik.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [PATCH 0/8] AMD opteron mm config numa etc


* Andrew Morton <akpm@...ux-foundation.org> wrote:

> On Wed, 20 Feb 2008 07:37:52 +0100 Ingo Molnar <mingo@...e.hu> wrote:
> 
> > Note: Andrew might get grumpy when 
> > your PCI tree starts changing nearby places in arch/x86/pci again and it 
> > clashes with these changes in x86.git
> 
> s/Andrew/Stephen/I hope/;)/
> 
> Hopefully we can soon start feeding these more problematic trees into 
> linux-next and yes, Stephen will need some more thought/support from 
> his upstreams to make that viable.

btw., the correct metric would be "real user-side regressions per 
commit" (maybe real regressions per line of code changed), not "number 
of commits". With the latter metric, x86.git is "problematic". For the 
former, it's much less so ;-)

i.e. you should punish buggy trees that affect real testers out there, 
not high-flux trees that by virtue of their flux cause more integration 
work.

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