From: Tejun Heo <tj@kernel.org>
To: Mike Snitzer <snitzer@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>, Jan Beulich <JBeulich@novell.com>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH v2.6.38-rc5 2/2] block: blk-flush shouldn't call directly into q->request_fn() __blk_run_queue()
Date: Fri, 18 Feb 2011 10:49:03 +0100 [thread overview]
Message-ID: <20110218094903.GF21209@htj.dyndns.org> (raw)
In-Reply-To: <AANLkTi=rPKN25yZTziv1dz=Ke0db8ZOwUgKFNzWn9+x7@mail.gmail.com>
On Thu, Feb 17, 2011 at 10:01:51AM -0500, Mike Snitzer wrote:
> Hi Tejun,
>
> On Thu, Feb 17, 2011 at 6:16 AM, Tejun Heo <tj@kernel.org> wrote:
>
> > Jens, this is applicable to v2.6.37 and 38. The new implementation
> > for 39 would need similar fix but I couldn't find where the tree is.
> > Which branch is it?
>
> for-2.6.39/core
Right, thanks. Jens, after you apply the two fixes for 2.6.38, I can
create a merge branch for for-2.6.39/core which you can pull. Would
that work for you?
Thanks.
--
tejun
next prev parent reply other threads:[~2011-02-18 9:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 11:15 [PATCH v2.6.38-rc5 1/2] block: add @force_kblockd to __blk_run_queue() Tejun Heo
2011-02-17 11:16 ` [PATCH v2.6.38-rc5 2/2] block: blk-flush shouldn't call directly into q->request_fn() __blk_run_queue() Tejun Heo
2011-02-17 15:01 ` Mike Snitzer
2011-02-18 9:49 ` Tejun Heo [this message]
2011-03-02 13:46 ` Jens Axboe
2011-03-04 18:25 ` Tejun Heo
2011-03-07 8:41 ` Jens Axboe
2011-03-07 19:33 ` Jeff Moyer
2011-03-07 19:36 ` Jens Axboe
2011-03-07 19:39 ` Jeff Moyer
2011-03-07 19:41 ` Jens Axboe
2011-03-07 19:50 ` Jeff Moyer
2011-03-08 7:54 ` Tejun Heo
2011-03-02 12:53 ` [PATCH v2.6.38-rc5 1/2] block: add @force_kblockd to __blk_run_queue() Jan Beulich
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=20110218094903.GF21209@htj.dyndns.org \
--to=tj@kernel.org \
--cc=JBeulich@novell.com \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@gmail.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 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®