From: Jens Axboe <axboe@kernel.dk>
To: Omar Sandoval <osandov@osandov.com>, linux-block@vger.kernel.org
Cc: kernel-team@fb.com, Hannes Reinecke <hare@suse.de>,
Ming Lei <ming.lei@redhat.com>, Karel Zak <kzak@redhat.com>,
Milan Broz <gmazyland@gmail.com>
Subject: Re: [PATCH v3 0/4] loop: LO_FLAGS_BLOCKSIZE fixes
Date: Tue, 22 Aug 2017 14:25:54 -0600 [thread overview]
Message-ID: <d4e4b9aa-d969-8bcd-38ee-47fc5b1b5d35@kernel.dk> (raw)
In-Reply-To: <cover.1503422996.git.osandov@fb.com>
On 08/22/2017 11:32 AM, Omar Sandoval wrote:
> From: Omar Sandoval <osandov@fb.com>
>
> Patches 1, 3, and 4 are the same as v2, plus added reviewed-bys and
> tested-bys from Milan. Patch 2 is new.
>
> Omar Sandoval (4):
> loop: fix hang if LOOP_SET_STATUS gets invalid blocksize or encrypt
> type
> loop: set discard and write zeroes limits in 512 byte sectors
> loop: use queue limit instead of private lo_logical_blocksize
> loop: always return block size in LOOP_GET_STATUS
Queued up, thanks Omar.
--
Jens Axboe
prev parent reply other threads:[~2017-08-22 20:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 17:32 [PATCH v3 0/4] loop: LO_FLAGS_BLOCKSIZE fixes Omar Sandoval
2017-08-22 17:32 ` [PATCH v3 1/4] loop: fix hang if LOOP_SET_STATUS gets invalid blocksize or encrypt type Omar Sandoval
2017-08-22 17:32 ` [PATCH v3 2/4] loop: set discard and write zeroes limits in 512 byte sectors Omar Sandoval
2017-08-23 6:19 ` Hannes Reinecke
2017-08-22 17:33 ` [PATCH v3 3/4] loop: use queue limit instead of private lo_logical_blocksize Omar Sandoval
2017-08-23 9:23 ` Karel Zak
2017-08-23 16:16 ` Omar Sandoval
2017-08-22 17:33 ` [PATCH v3 4/4] loop: always return block size in LOOP_GET_STATUS Omar Sandoval
2017-08-22 20:25 ` Jens Axboe [this message]
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=d4e4b9aa-d969-8bcd-38ee-47fc5b1b5d35@kernel.dk \
--to=axboe@kernel.dk \
--cc=gmazyland@gmail.com \
--cc=hare@suse.de \
--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.