From: Hannes Reinecke <hare@suse.de>
To: Omar Sandoval <osandov@osandov.com>, linux-block@vger.kernel.org
Cc: kernel-team@fb.com, Ming Lei <ming.lei@redhat.com>,
Karel Zak <kzak@redhat.com>, Milan Broz <gmazyland@gmail.com>
Subject: Re: [PATCH 1/4] loop: get rid of lo_blocksize
Date: Thu, 24 Aug 2017 14:22:49 +0200 [thread overview]
Message-ID: <d4e08c2c-0954-a8fd-e72d-db511df1cf45@suse.de> (raw)
In-Reply-To: <ef0f206cb2c75da3b850c59ea7b7efc0b94f4b32.1503558155.git.osandov@fb.com>
On 08/24/2017 09:03 AM, Omar Sandoval wrote:
> From: Omar Sandoval <osandov@fb.com>
>
> This is only used for setting the soft block size on the struct
> block_device once and then never used again.
>
> Signed-off-by: Omar Sandoval <osandov@fb.com>
> ---
> drivers/block/loop.c | 10 ++--------
> drivers/block/loop.h | 1 -
> 2 files changed, 2 insertions(+), 9 deletions(-)
>
Reviewed-by: Hannes Reinecke <hare@suse.com>
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2017-08-24 12:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 7:03 [PATCH 0/4] loop: support different logical block sizes Omar Sandoval
2017-08-24 7:03 ` [PATCH 1/4] loop: get rid of lo_blocksize Omar Sandoval
2017-08-24 12:22 ` Hannes Reinecke [this message]
2017-08-24 7:03 ` [PATCH 2/4] loop: set physical block size to PAGE_SIZE Omar Sandoval
2017-08-24 12:23 ` Hannes Reinecke
2017-08-24 7:03 ` [PATCH 3/4] loop: add ioctl for changing logical block size Omar Sandoval
2017-08-24 8:06 ` Karel Zak
2017-08-24 16:31 ` Omar Sandoval
2017-08-24 12:25 ` Hannes Reinecke
2017-08-24 7:03 ` [PATCH 4/4] loop: fold loop_switch() into callers Omar Sandoval
2017-08-24 12:25 ` Hannes Reinecke
2017-08-29 11:33 ` [PATCH 0/4] loop: support different logical block sizes Ming Lei
2017-08-31 19:51 ` Jens Axboe
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=d4e08c2c-0954-a8fd-e72d-db511df1cf45@suse.de \
--to=hare@suse.de \
--cc=gmazyland@gmail.com \
--cc=kernel-team@fb.com \
--cc=kzak@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=osandov@osandov.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.