All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Greg KH <greg@kroah.com>, Yinghai Lu <Yinghai.Lu@Sun.COM>,
	Jeff Garzik <jeff@garzik.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH 0/8] AMD opteron mm config numa etc
Date: Wed, 20 Feb 2008 11:38:31 +0100	[thread overview]
Message-ID: <20080220103831.GH3881@elte.hu> (raw)
In-Reply-To: <20080220015115.a5989384.akpm@linux-foundation.org>


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

> On Wed, 20 Feb 2008 07:37:52 +0100 Ingo Molnar <mingo@elte.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

  reply	other threads:[~2008-02-20 10:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-19 11:19 [PATCH 0/8] AMD opteron mm config numa etc Yinghai Lu
2008-02-19 11:23 ` Ingo Molnar
2008-02-19 17:53   ` Greg KH
2008-02-20  6:37     ` Ingo Molnar
2008-02-20  9:51       ` Andrew Morton
2008-02-20 10:38         ` Ingo Molnar [this message]
2008-02-19 16:50 ` Jeff Garzik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080220103831.GH3881@elte.hu \
    --to=mingo@elte.hu \
    --cc=Yinghai.Lu@Sun.COM \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.