public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: akataria@vmware.com, Ingo Molnar <mingo@elte.hu>,
	"Brown, Len" <len.brown@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-acpi <linux-acpi@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	TJ <linux@tjworld.net>
Subject: Re: acpi based pci gap calculation  - v3
Date: Wed, 16 Jul 2008 18:33:46 +0200	[thread overview]
Message-ID: <487E22EA.8030005@linux.intel.com> (raw)
In-Reply-To: <200807160906.43632.jbarnes@virtuousgeek.org>


> The only problem there is that linux-next doesn't get nearly the sort of 
> testing coverage we need for this kind of change.

Normally I tend to wait for one -mm release, which seems to be tested
by a reasonable number of people. If it survives that it is good
to be tested in Linus' tree.

Just stuffing this in in literally the last minute doesn't seem
like a good idea.

-Andi

  reply	other threads:[~2008-07-16 16:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15 18:59 acpi based pci gap calculation - v3 Alok Kataria
2008-07-15 20:28 ` Jesse Barnes
2008-07-15 20:54   ` Alok Kataria
2008-07-15 22:53     ` Jesse Barnes
2008-07-15 23:07       ` Ingo Molnar
2008-07-16  5:40       ` Andi Kleen
2008-07-16 16:06         ` Jesse Barnes
2008-07-16 16:33           ` Andi Kleen [this message]
2008-07-17  0:03             ` Jesse Barnes
2008-07-17 21:31               ` Alok Kataria
     [not found]                 ` <1216663147.26169.5.camel@alok-dev1>
     [not found]                   ` <200807221450.52114.jbarnes@virtuousgeek.org>
2008-07-22 22:52                     ` Alok Kataria
2008-07-23  7:13                       ` TJ
2008-07-23 16:58                       ` Jesse Barnes
2008-07-23 17:10                         ` Alok Kataria
2008-07-23 17:52                           ` Jesse Barnes
2008-07-23 18:02                             ` Alok Kataria
2008-07-16  5:42 ` Andi Kleen

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=487E22EA.8030005@linux.intel.com \
    --to=ak@linux.intel.com \
    --cc=akataria@vmware.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux@tjworld.net \
    --cc=mingo@elte.hu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox