lkml.org 
[lkml]   [2011]   [Nov]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCH pm] freezer: fix wait_event_freezable/__thaw_task races
Date
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


\
 
 \ /
  Last update: 2011-11-03 23:13    [W:0.049 / U:11.316 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site