From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
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 10:20:00 +1100 [thread overview]
Message-ID: <20120125102000.df33159bdc5f627730d9b1b4@canb.auug.org.au> (raw)
In-Reply-To: <201201250018.16848.rjw@sisk.pl>
[-- Attachment #1: Type: text/plain, Size: 1676 bytes --]
Hi Rafael,
On Wed, 25 Jan 2012 00:18:16 +0100 "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
>
> 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.
There are no commits in next-20120124 that touch either of those files.
Since v3.2 we have these (so in the merge window and Linus' tree):
$ git shortlog v3.2..master kernel/workqueue.c kernel/freezer.c
Tejun Heo (17):
freezer: fix current->state restoration race in refrigerator()
freezer: unexport refrigerator() and update try_to_freeze() slightly
freezer: implement and use kthread_freezable_should_stop()
freezer: rename thaw_process() to __thaw_task() and simplify the implement
freezer: use dedicated lock instead of task_lock() + memory barrier
freezer: make freezing indicate freeze condition in effect
freezer: test freezable conditions while holding freezer_lock
freezer: kill PF_FREEZING
freezer: clean up freeze_processes() failure path
freezer: make freezing() test freeze conditions in effect instead of TIF_F
freezer: remove should_send_signal() and update frozen()
freezer: fix set_freezable[_with_signal]() race
freezer: restructure __refrigerator()
freezer: use lock_task_sighand() in fake_signal_wake_up()
freezer: remove unused @sig_only from freeze_task()
freezer: kill unused set_freezable_with_signal()
workqueue: make alloc_workqueue() take printf fmt and args for name
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-01-24 23:20 UTC|newest]
Thread overview: 16+ 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 ` linux-next: Tree for Jan 24 Rafael J. Wysocki
2012-01-24 23:20 ` Stephen Rothwell [this message]
2013-01-24 6:13 Stephen Rothwell
2014-01-24 4:40 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
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=20120125102000.df33159bdc5f627730d9b1b4@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rjw@sisk.pl \
--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).