From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Tejun Heo <tj@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (pm tree related)
Date: Thu, 24 Nov 2011 11:15:05 +0100 [thread overview]
Message-ID: <201111241115.05836.rjw@sisk.pl> (raw)
In-Reply-To: <CAOS58YPAh3e_sa4JrHdVD40scNED5Z4g4t6JNU8MT8kq8vZV2Q@mail.gmail.com>
On Thursday, November 24, 2011, Tejun Heo wrote:
> Hello,
>
> On Wed, Nov 23, 2011 at 10:19 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >> > Subject: [PATCH] freezer: fix more fallout from the thaw_process rename
> >> >
> >> > Commit 944e192db53c "freezer: rename thaw_process() to __thaw_task()
> >> > and simplify the implementation" did not create a !CONFIG_FREEZER version
> >> > of __thaw_task().
> >> >
> >> > Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> >>
> >> I've applied your patch to linux-pm/pm-freezer and merged it into
> >> linux-pm/linux-next.
>
> Ah.. that's my bad. I was actually looking at that diff and somehow it
> just slipped my mind. Rafael, can you please apply Stephen's patch on
> top of pm-freezer?
Sure, I will do that later today.
Thanks,
Rafael
next prev parent reply other threads:[~2011-11-24 10:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 3:24 linux-next: build failure after merge of the final tree (pm tree related) Stephen Rothwell
2011-11-14 23:12 ` Rafael J. Wysocki
2011-11-24 6:19 ` Stephen Rothwell
2011-11-24 6:32 ` Tejun Heo
2011-11-24 10:15 ` Rafael J. Wysocki [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-24 3:44 Stephen Rothwell
2012-10-24 3:58 ` Song, Youquan
2012-10-24 21:40 ` Rafael J. Wysocki
2011-12-22 5:28 Stephen Rothwell
2011-12-23 0:32 ` Rafael J. Wysocki
2011-08-19 3:03 Stephen Rothwell
2011-08-19 8:14 ` Pihet-XID, Jean
2011-08-19 13:39 ` Stephen Rothwell
2011-08-19 20:33 ` Randy Dunlap
2011-08-19 21:58 ` Rafael J. Wysocki
2011-08-20 7:50 ` Pihet-XID, Jean
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=201111241115.05836.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tj@kernel.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;
as well as URLs for NNTP newsgroup(s).