public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: trenn@suse.de, linux-acpi <linux-acpi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Len Brown <lenb@kernel.org>
Subject: Re: [PATCH 0/5] Detect hwmon and i2c bus drivers interfering with  ACPI Operation Region resources
Date: Thu, 25 Oct 2007 15:51:35 +0200	[thread overview]
Message-ID: <20071025155135.019baca3@hyperion.delvare> (raw)
In-Reply-To: <20071024205723.458fab97.akpm@linux-foundation.org>

On Wed, 24 Oct 2007 20:57:23 -0700, Andrew Morton wrote:
> On Wed, 24 Oct 2007 16:31:59 +0200 Thomas Renninger <trenn@suse.de> wrote:
> 
> > it seems Len's test tree and Linus tree diverged a bit, at least with
> > this patch set things do not apply cleanly.
> > 
> > Therefore I post these for discussion whether and in which kernel tree
> > they should end up before doing work for nothing.
> > If they are still a candidate for 2.6.24 (rather unintrusive), pls tell
> > me whether and when I should base them against Len's test/release branch
> > or whatever other tree.
> > If not, it would be great if they can be included into the -mm tree and
> > I can rebase them against this one.
> 
> I staged the three acpi patches against Len's tree and I staged the hwmon
> patch against Mark's tree and I staged the I2C patch against Jean's tree.
> 
> This means that if/when the ACPI patches have gone me->Len->Linus, I can
> send the I2C patch to Jean and the hwmon patch to Mark and we're all good.

Thanks for picking these patches, having them in -mm for some time is
exactly what we need. Let's see how many systems are affected by the
resource conflicts and how we can fix them

-- 
Jean Delvare

  reply	other threads:[~2007-10-25 13:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24 14:31 [PATCH 0/5] Detect hwmon and i2c bus drivers interfering with ACPI Operation Region resources Thomas Renninger
2007-10-25  3:57 ` Andrew Morton
2007-10-25 13:51   ` Jean Delvare [this message]
2007-10-25 20:24     ` Andrew Morton
2007-10-26 19:23       ` Jean Delvare
2007-10-25 12:04 ` Mark M. Hoffman
2007-10-25 15:54   ` Jean Delvare
2007-10-25 15:06 ` Bjorn Helgaas
2007-10-25 22:55   ` Thomas Renninger
2007-10-26  3:59     ` Bjorn Helgaas
2007-10-26 10:45       ` Thomas Renninger
2007-10-26 13:09         ` Bjorn Helgaas
2007-10-26 20:39           ` Jean Delvare
2007-10-27 15:09   ` Matthew Garrett
2007-10-29  2:50     ` Bjorn Helgaas
2007-10-29 13:11       ` Matthew Garrett
2007-10-30 18:43       ` Jean Delvare
2007-10-25 21:36 ` Len Brown

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=20071025155135.019baca3@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=akpm@linux-foundation.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trenn@suse.de \
    /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