From: Tejun Heo <htejun@gmail.com>
To: jeff@garzik.org, linux-ide@vger.kernel.org,
jens.axboe@oracle.com, linux-scsi@vger.kernel.org,
James.Bottomley@suse.de, linux-kernel@vger.kernel.org,
ben@decadent.org.uk, davem@daveml
Subject: Re: [PATCHSET] block,libata: implement ->unlock_native_capacity()
Date: Wed, 19 May 2010 09:05:40 +0200 [thread overview]
Message-ID: <4BF38DC4.3090900@gmail.com> (raw)
In-Reply-To: <1273946974-29131-1-git-send-email-tj@kernel.org>
On 05/15/2010 08:09 PM, Tejun Heo wrote:
> Hello, all.
>
> This is the evolved version of the implement-set_capacity patchset[L]
> and contains the following patches.
>
> 0001-buffer-make-invalidate_bdev-drain-all-percpu-LRU-add.patch
> 0002-block-restart-partition-scan-after-resizing-a-device.patch
> 0003-block-ide-simplify-bdops-set_capacity-to-unlock_nati.patch
> 0004-block-use-struct-parsed_partitions-state-universally.patch
> 0005-block-improve-automatic-native-capacity-unlocking.patch
> 0006-SCSI-implement-sd_unlock_native_capacity.patch
> 0007-libata-use-the-enlarged-capacity-after-late-HPA-unlo.patch
> 0008-libata-implement-on-demand-HPA-unlocking.patch
Other than block part, everything is acked, so how do we route this?
0001-0005 through block tree and 0006-0008 through libata tree seem
the easiest unless someone objects. Jens, can you please review
0001-0005 and take them into block tree if it seems okay?
Thanks.
--
tejun
next prev parent reply other threads:[~2010-05-19 7:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-15 18:09 [PATCHSET] block,libata: implement ->unlock_native_capacity() Tejun Heo
2010-05-15 18:09 ` [PATCH 1/8] buffer: make invalidate_bdev() drain all percpu LRU add caches Tejun Heo
2010-05-16 7:11 ` David Miller
2010-05-15 18:09 ` [PATCH 2/8] block: restart partition scan after resizing a device Tejun Heo
2010-05-16 7:15 ` David Miller
2010-05-15 18:09 ` [PATCH 3/8] block,ide: simplify bdops->set_capacity() to ->unlock_native_capacity() Tejun Heo
2010-05-15 18:48 ` Bartlomiej Zolnierkiewicz
2010-05-15 18:58 ` Tejun Heo
2010-05-16 7:15 ` David Miller
2010-05-15 18:09 ` [PATCH 4/8] block: use struct parsed_partitions *state universally in partition check code Tejun Heo
2010-05-16 7:16 ` David Miller
2010-05-15 18:09 ` [PATCH 5/8] block: improve automatic native capacity unlocking Tejun Heo
2010-05-16 7:17 ` David Miller
2010-05-15 18:09 ` [PATCH 6/8] SCSI: implement sd_unlock_native_capacity() Tejun Heo
2010-05-16 7:18 ` David Miller
2010-05-16 13:39 ` James Bottomley
2010-05-16 15:07 ` Ben Hutchings
2010-05-16 16:00 ` James Bottomley
2010-05-16 17:00 ` Tejun Heo
2010-05-16 19:23 ` James Bottomley
2010-05-17 5:30 ` Tejun Heo
2010-06-02 17:50 ` Jeff Garzik
2010-05-15 18:09 ` [PATCH 7/8] libata: use the enlarged capacity after late HPA unlock Tejun Heo
2010-05-15 19:22 ` Jeff Garzik
2010-05-16 7:18 ` David Miller
2010-05-15 18:09 ` [PATCH 8/8] libata: implement on-demand HPA unlocking Tejun Heo
2010-05-15 19:22 ` Jeff Garzik
2010-05-16 7:19 ` David Miller
2010-05-19 7:05 ` Tejun Heo [this message]
2010-05-19 7:08 ` [PATCHSET] block,libata: implement ->unlock_native_capacity() Jens Axboe
2010-06-02 16:37 ` Tejun Heo
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=4BF38DC4.3090900@gmail.com \
--to=htejun@gmail.com \
--cc=James.Bottomley@suse.de \
--cc=ben@decadent.org.uk \
--cc=davem@daveml \
--cc=jeff@garzik.org \
--cc=jens.axboe@oracle.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.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;
as well as URLs for NNTP newsgroup(s).