From: Jens Axboe <jens.axboe@oracle.com>
To: Romit Dasgupta <romit@ti.com>
Cc: "linux-pm@lists.linux-foundation.org"
<linux-pm@lists.linux-foundation.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1]: Thaws refrigerated bdi flusher threads before invoking kthread_stop on them
Date: Thu, 12 Nov 2009 13:05:47 +0100 [thread overview]
Message-ID: <20091112120546.GI8742@kernel.dk> (raw)
In-Reply-To: <1258026726.2341.1.camel@boson>
On Thu, Nov 12 2009, Romit Dasgupta wrote:
> Resubmitting after incorporationg the suggestions:
> >
> > Romit, please rework as suggested by Jens and resubmit.
>
> Unfreezes the bdi flusher task when the said task needs to exit.
Thanks, this looks more palatable. I will merge it and make sure it goes
upstream soon.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <jens.axboe@oracle.com>
To: Romit Dasgupta <romit@ti.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Pavel Machek <pavel@ucw.cz>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-pm@lists.linux-foundation.org"
<linux-pm@lists.linux-foundation.org>
Subject: Re: [PATCH 1/1]: Thaws refrigerated bdi flusher threads before invoking kthread_stop on them
Date: Thu, 12 Nov 2009 13:05:47 +0100 [thread overview]
Message-ID: <20091112120546.GI8742@kernel.dk> (raw)
In-Reply-To: <1258026726.2341.1.camel@boson>
On Thu, Nov 12 2009, Romit Dasgupta wrote:
> Resubmitting after incorporationg the suggestions:
> >
> > Romit, please rework as suggested by Jens and resubmit.
>
> Unfreezes the bdi flusher task when the said task needs to exit.
Thanks, this looks more palatable. I will merge it and make sure it goes
upstream soon.
--
Jens Axboe
next prev parent reply other threads:[~2009-11-12 12:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 8:30 [PATCH 1/1]: Thaws refrigerated bdi flusher threads before invoking kthread_stop on them Romit Dasgupta
2009-11-11 10:34 ` Pavel Machek
2009-11-11 11:30 ` Rafael J. Wysocki
2009-11-11 11:30 ` Rafael J. Wysocki
2009-11-11 11:50 ` Romit Dasgupta
2009-11-11 11:59 ` Rafael J. Wysocki
2009-11-11 11:59 ` Rafael J. Wysocki
2009-11-11 11:50 ` Romit Dasgupta
2009-11-11 19:37 ` Jens Axboe
2009-11-11 20:41 ` Rafael J. Wysocki
2009-11-12 11:52 ` Romit Dasgupta
2009-11-12 12:05 ` Jens Axboe [this message]
2009-11-12 12:05 ` Jens Axboe
2009-11-12 11:52 ` Romit Dasgupta
2009-11-11 20:41 ` Rafael J. Wysocki
2009-11-11 19:37 ` Jens Axboe
2009-11-11 10:34 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2009-11-11 8:30 Romit Dasgupta
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=20091112120546.GI8742@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=romit@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.