From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@fb.com>, Alexander Graf <agraf@suse.com>,
Ming@suse.de, "\"Lei" <"tom.leiming\""@gmail.co>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] loop: Pass logical blocksize in 'lo_init[0]' ioctl field
Date: Tue, 1 Nov 2016 17:58:19 +0100 [thread overview]
Message-ID: <c961affe-3b77-8ecb-e3ec-44955f5d3729@suse.de> (raw)
In-Reply-To: <20161101140208.GC16815@lst.de>
On 11/01/2016 03:02 PM, Christoph Hellwig wrote:
> On Mon, Oct 31, 2016 at 08:37:19PM +0100, Hannes Reinecke wrote:
>> The current LOOP_SET_STATUS64 ioctl has two unused fields
>> 'init[2]', which can be used in conjunction with the
>> LO_FLAGS_BLOCKSIZE flag to pass in the new logical blocksize.
>
> Can we give them sane field names while at it? Also I see now reason
> not to merge this with the previous two patches.
>
Sure I can rename it.
As for merging, I don't really care.
So for the next round I'll be merging them all together.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2016-11-01 16:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 19:37 [PATCHv3 0/4] loop: enable different physical blocksizes Hannes Reinecke
2016-10-31 19:37 ` [PATCH 1/4] loop: Remove unused 'bdev' argument from loop_set_capacity Hannes Reinecke
2016-10-31 21:26 ` Ming Lei
2016-10-31 19:37 ` [PATCH 2/4] loop: Enable correct physical blocksize Hannes Reinecke
2016-11-01 14:00 ` Christoph Hellwig
2016-10-31 19:37 ` [PATCH 3/4] loop: Add 'lo_logical_blocksize' Hannes Reinecke
2016-11-01 14:01 ` Christoph Hellwig
2016-11-01 16:57 ` Hannes Reinecke
2016-10-31 19:37 ` [PATCH 4/4] loop: Pass logical blocksize in 'lo_init[0]' ioctl field Hannes Reinecke
2016-11-01 14:02 ` Christoph Hellwig
2016-11-01 16:58 ` Hannes Reinecke [this message]
2016-11-03 13:26 ` Hannes Reinecke
-- strict thread matches above, loose matches on Subject: below --
2015-11-10 8:13 [PATCHv3 0/4] loop: enable different physical blocksizes Hannes Reinecke
2015-11-10 8:13 ` [PATCH 4/4] loop: Pass logical blocksize in 'lo_init[0]' ioctl field Hannes Reinecke
2015-11-13 21:42 ` Jeff Moyer
2015-08-07 8:54 [PATCHv2 0/4] loop: enable different physical blocksizes Hannes Reinecke
2015-08-07 8:54 ` [PATCH 4/4] loop: Pass logical blocksize in 'lo_init[0]' ioctl field Hannes Reinecke
2015-07-17 7:27 [PATCH 0/4] loop: enable different physical blocksizes Hannes Reinecke
2015-07-17 7:27 ` [PATCH 4/4] loop: Pass logical blocksize in 'lo_init[0]' ioctl field Hannes Reinecke
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=c961affe-3b77-8ecb-e3ec-44955f5d3729@suse.de \
--to=hare@suse.de \
--cc="tom.leiming\""@gmail.co \
--cc=Ming@suse.de \
--cc=agraf@suse.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=linux-kernel@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).