From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: sedat.dilek@gmail.com, Andi Kleen <ak@linux.intel.com>,
len.brown@intel.com, Linux ACPI <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git pull request] ACPI patches for 2.6.36.merge
Date: Sun, 15 Aug 2010 18:21:53 -0700 [thread overview]
Message-ID: <20100815182153.994179c1.akpm@linux-foundation.org> (raw)
In-Reply-To: <AANLkTi=Ok3NH3k5EF1Da2Z3xA7uahABRtH7pEdOEuZH2@mail.gmail.com>
On Sun, 15 Aug 2010 14:04:09 -0700 Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Sun, Aug 15, 2010 at 1:30 PM, Andrew Morton
> <akpm@linux-foundation.org> wrote:
> >
> > I'd be suspecting that we have two patches both of which worked
> > separately but which broke when combined. Is there some other patch in
> > that tree which adds a new reference to `ref' in acpi_power_seq_show()?
>
> The offending patch isn't about acpi_power_seq_show(), it's about
> acpi_power_off_device().
The patch I sent Len patched acpi_power_seq_show().
>
> ...
>
> What does that say about the _rest_ of the patches?
Not tested in combination?
> What does that say about (lack of) -next testing?
That code compiled OK in -mm which includes linux-next. I assume that
some last-minute merging broke things.
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-08-16 1:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-15 10:41 [git pull request] ACPI patches for 2.6.36.merge Sedat Dilek
2010-08-15 11:13 ` Sedat Dilek
2010-08-15 18:15 ` Linus Torvalds
2010-08-15 20:30 ` Andrew Morton
2010-08-15 21:04 ` Linus Torvalds
2010-08-16 1:21 ` Andrew Morton [this message]
2010-08-16 1:35 ` Linus Torvalds
2010-08-16 2:43 ` Stephen Rothwell
2010-08-24 22:35 ` Len Brown
-- strict thread matches above, loose matches on Subject: below --
2010-08-15 5:12 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=20100815182153.994179c1.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ak@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=torvalds@linux-foundation.org \
/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