From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH pm] freezer: fix wait_event_freezable/__thaw_task races
Date: Thu, 3 Nov 2011 23:12:59 +0100 [thread overview]
Message-ID: <201111032313.00082.rjw@sisk.pl> (raw)
In-Reply-To: <20111103150708.GC4417@google.com>
On Thursday, November 03, 2011, Tejun Heo wrote:
> Hello, Rafael.
>
> On Thu, Nov 03, 2011 at 11:43:13AM +0100, Rafael J. Wysocki wrote:
> > On Thursday, November 03, 2011, Tejun Heo wrote:
> > > Hello,
> > >
> > > On Wed, Nov 2, 2011 at 6:01 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > > > OK, so I guess I should drop it from my linux-next branch?
> > >
> > > Hmmm... yes, the preceding patches should be applied first and then
> > > this one. Any problems with earlier ones?
> >
> > The only problem I currently have is to figure out what patches to apply
> > and in which order. Care to help? ;-)
>
> Heh, sorry about that, so to sum up the outstanding patches.
>
> for-fixes (current merge window)
>
> [1] wait_event_freezekillable: use freezer_do_not_count/freezer_count
> [2] freezer: revert 27920651fe "PM / Freezer: Make fake_signal_wake_up() wake TASK_KILLABLE tasks too"
>
> It would be a good idea to note that the first patch makes thes
> change made by commit 27920651fe and thus reverting is safe.
OK
Can you repost these two with new changelogs so that there's no confusion
about what they are doing and why exactly, pretty please?
> for-next
>
> [3] freezer: fix various bugs and simplify implementation, take#2
> [4] usb_storage: don't use set_freezable_with_signal()
> [5] freezer: kill unused set_freezable_with_signal()
> [6] freezer: fix wait_event_freezable/__thaw_task races
>
> All the for-next patches are in the following git branch in the above
> order.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git pm-fix-wait_freezable
Good. I'll put them into a separate branch and merge them into my linux-next
branch when 3.2-rc1 is out.
Thanks,
Rafael
next prev parent reply other threads:[~2011-11-03 22:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 2:15 Tejun Heo
2011-11-03 0:20 ` Rafael J. Wysocki
2011-11-03 0:43 ` Tejun Heo
2011-11-03 1:01 ` Rafael J. Wysocki
2011-11-03 6:38 ` Tejun Heo
2011-11-03 10:43 ` Rafael J. Wysocki
2011-11-03 15:07 ` Tejun Heo
2011-11-03 22:12 ` Rafael J. Wysocki [this message]
2011-11-03 22:16 ` Tejun Heo
2011-11-03 22:22 ` Rafael J. Wysocki
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=201111032313.00082.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=oleg@redhat.com \
--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
all inboxes | Powered by JetHome®