linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>, Jiri Slaby <jslaby@suse.cz>
Subject: Re: linux-next: Tree for Jan 24
Date: Wed, 25 Jan 2012 00:18:16 +0100	[thread overview]
Message-ID: <201201250018.16848.rjw@sisk.pl> (raw)
In-Reply-To: <20120124163055.3c99bca0d5dfd754a352fb02@canb.auug.org.au>

Hi Stephen,

On Tuesday, January 24, 2012, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20120123:
> 
> New tree: ktest
> Reinstated tree: input-mt
> 
> My fixes tree contains:
> 	powerpc: make PSERIES_IDLE bool
> 
> Linus' tree gained a build failure for which I applied a patch.
> 
> The arm tree gained a conflict against Linus' tree.
> 
> The arm-soc tree lost its conflicts but gained another against the arm
> tree.
> 
> The s5p tree gained conflicts against Linus' tree.
> 
> The nfs tree lost its build failure.
> 
> The sound-asoc tree lost its build failure.
> 
> The input tree gained a build failure so I used the version from
> next-20120123.
> 
> The akpm tree lost several patches that were merged into Linus' tree.

Is there any new material touching kernel/workqueue.c or kernel/freezer.c?

We seem to have a freezer regression in linux-next which doesn't seem to be
present in my tree.

Thanks,
Rafael

  parent reply	other threads:[~2012-01-24 23:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-24  5:30 linux-next: Tree for Jan 24 Stephen Rothwell
2012-01-24 18:26 ` linux-next: Tree for Jan 24 (regulator/mc13892-regulator) Randy Dunlap
2012-01-24 19:10   ` Mark Brown
2012-01-24 18:37 ` linux-next: Tree for Jan 24 (usb/otg/mv_otg) Randy Dunlap
2012-01-30  3:48   ` Neil Zhang
2012-01-24 23:18 ` Rafael J. Wysocki [this message]
2012-01-24 23:20   ` linux-next: Tree for Jan 24 Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2013-01-24  6:13 Stephen Rothwell
2014-01-24  4:40 Stephen Rothwell
2014-01-27 17:47 ` Paul Gortmaker
2014-01-27 23:28   ` Stephen Rothwell
2014-01-27 17:58 ` Paul Gortmaker
2017-01-24  5:46 Stephen Rothwell
2019-01-24  6:29 Stephen Rothwell
2020-01-24  6:33 Stephen Rothwell
2022-01-24  0:35 Stephen Rothwell
2023-01-24  3:40 Stephen Rothwell
2024-01-24  4:36 Stephen Rothwell
2025-01-24  4:51 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=201201250018.16848.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=jslaby@suse.cz \
    --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).