From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Tejun Heo <tj@kernel.org>
Subject: Re: linux-next: Tree for Nov 15
Date: Tue, 15 Nov 2011 22:03:26 +0100 [thread overview]
Message-ID: <201111152203.26186.rjw@sisk.pl> (raw)
In-Reply-To: <20111115131742.f9ebaf818fd152ef779f4d19@canb.auug.org.au>
On Tuesday, November 15, 2011, Stephen Rothwell wrote:
> Hi all,
>
> The patch is still absent from kernel.org.
>
> Changes since 20111114:
>
> The m86knommu tree lost 2 conflicts.
>
> The pm tree still had its build failures for which I reverted a commit
> and applied a patch.
Hmm. If that was the patch you sent yestarday, it definitely is there in my
tree.
The "kill unused set_freezable_with_signal()" commit still has to be reverted,
unfortunately, but Tejun is working on a fix (AFAICS).
I'm going to drop pm-freezer from my linux-next branch for now.
Thanks,
Rafael
next prev parent reply other threads:[~2011-11-15 21:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 2:17 linux-next: Tree for Nov 15 Stephen Rothwell
2011-11-15 21:03 ` Rafael J. Wysocki [this message]
2011-11-16 1:04 ` [PATCH -next] staging: fix more ET131X build errors Randy Dunlap
2011-11-17 10:48 ` Mark Einon
2012-11-15 7:17 linux-next: Tree for Nov 15 Stephen Rothwell
2013-11-15 5:24 Stephen Rothwell
2015-11-15 2:31 Stephen Rothwell
2016-11-15 4:13 Stephen Rothwell
2017-11-15 5:47 Stephen Rothwell
2018-11-15 4:45 Stephen Rothwell
2019-11-15 8:05 Stephen Rothwell
2019-11-15 16:11 ` Naresh Kamboju
2021-11-15 1:47 Stephen Rothwell
2022-11-15 7:20 Stephen Rothwell
2023-11-15 1:27 Stephen Rothwell
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=201111152203.26186.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).