From: Jens Axboe <jaxboe@fusionio.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Shaohua Li <shaohua.li@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"hch@infradead.org" <hch@infradead.org>,
"jgarzik@pobox.com" <jgarzik@pobox.com>,
"djwong@us.ibm.com" <djwong@us.ibm.com>,
"sshtylyov@mvista.com" <sshtylyov@mvista.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"ricwheeler@gmail.com" <ricwheeler@gmail.com>
Subject: Re: [patch v3 2/3] block: hold queue if flush is running for non-queueable flush drive
Date: Fri, 6 May 2011 11:28:54 -0600 [thread overview]
Message-ID: <4DC42FD6.8010508@fusionio.com> (raw)
In-Reply-To: <20110506065347.GA8824@htj.dyndns.org>
On 2011-05-06 00:53, Tejun Heo wrote:
> Jens, can you please queue this for the next merge window?
Yep I will, I'll mark it as a backport as well.
--
Jens Axboe
next prev parent reply other threads:[~2011-05-06 17:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 1:59 [patch v3 0/3] block: optimize flush for non-queueable flush drive shaohua.li
2011-05-05 1:59 ` [patch v3 1/3] block: add a non-queueable flush flag shaohua.li
2011-05-05 2:17 ` Jeff Garzik
2011-05-05 2:21 ` Shaohua Li
2011-05-05 7:53 ` Tejun Heo
2011-05-05 1:59 ` [patch v3 2/3] block: hold queue if flush is running for non-queueable flush drive shaohua.li
2011-05-05 8:38 ` Tejun Heo
2011-05-06 4:32 ` Shaohua Li
2011-05-06 6:53 ` Tejun Heo
2011-05-06 17:28 ` Jens Axboe [this message]
2011-05-09 13:03 ` Vivek Goyal
2011-05-09 13:50 ` Shaohua Li
2011-05-09 13:58 ` Vivek Goyal
2011-05-09 14:37 ` Tejun Heo
2011-05-05 1:59 ` [patch v3 3/3] SATA: enable non-queueable flush flag shaohua.li
2011-05-05 7:54 ` Tejun Heo
2011-05-05 12:33 ` Jeff Garzik
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=4DC42FD6.8010508@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=djwong@us.ibm.com \
--cc=hch@infradead.org \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ricwheeler@gmail.com \
--cc=shaohua.li@intel.com \
--cc=sshtylyov@mvista.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.