public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: Jens Axboe <axboe@fb.com>, Alexander Graf <agraf@suse.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] loop: Enable correct physical blocksize
Date: Fri, 7 Aug 2015 09:31:43 +0200	[thread overview]
Message-ID: <20150807073142.GA17618@lst.de> (raw)
In-Reply-To: <55B5C8D3.1000507@suse.de>

On Mon, Jul 27, 2015 at 07:59:47AM +0200, Hannes Reinecke wrote:
> On 07/27/2015 07:15 AM, Christoph Hellwig wrote:
> > On Fri, Jul 17, 2015 at 09:27:04AM +0200, Hannes Reinecke wrote:
> >> When running on files the physical blocksize is actually 4k,
> >> so we should be announcing it as such. This is enabled with
> >> a new LO_FLAGS_BLOCKSIZE flag value to the existing ioctl.
> > 
> > The flag is only used in this patch, but not actually defined anywhere.
> > 
> Ah, Merge error.
> I'll fix it up.

Can you resen the series?

  reply	other threads:[~2015-08-07  7:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-17  7:27 [PATCH 0/4] loop: enable different physical blocksizes Hannes Reinecke
2015-07-17  7:27 ` [PATCH 1/4] loop: Enable correct physical blocksize Hannes Reinecke
2015-07-27  5:15   ` Christoph Hellwig
2015-07-27  5:59     ` Hannes Reinecke
2015-08-07  7:31       ` Christoph Hellwig [this message]
2015-07-17  7:27 ` [PATCH 2/4] loop: Remove unused 'bdev' argument from loop_set_capacity Hannes Reinecke
2015-07-27  5:16   ` Christoph Hellwig
2015-07-17  7:27 ` [PATCH 3/4] loop: Add 'lo_logical_blocksize' Hannes Reinecke
2015-07-17  7:27 ` [PATCH 4/4] loop: Pass logical blocksize in 'lo_init[0]' ioctl field Hannes Reinecke
2015-07-27 10:40 ` [PATCH 0/4] loop: enable different physical blocksizes Ming Lei
2015-08-03 23:00   ` Alexander Graf
2015-08-07  5:07     ` Ming Lei
2015-08-07  6:46       ` Hannes Reinecke
2015-08-07  7:23         ` Ming Lei
2015-08-07  7:45           ` Hannes Reinecke
2015-08-07  8:02             ` Ming Lei
2015-08-07  7:33   ` Christoph Hellwig
2015-08-07  7:44     ` Ming Lei
2015-08-07  7:48       ` Christoph Hellwig
2015-08-07  7:58         ` Ming Lei
2015-08-07  7:50       ` Hannes Reinecke
  -- strict thread matches above, loose matches on Subject: below --
2015-11-10  8:13 [PATCHv3 " Hannes Reinecke
2015-11-10  8:13 ` [PATCH 1/4] loop: Enable correct physical blocksize Hannes Reinecke
2015-11-13 20:57   ` Jeff Moyer
2015-12-01  9:32     ` Hannes Reinecke
2015-11-20  3:12   ` Ming Lei

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=20150807073142.GA17618@lst.de \
    --to=hch@lst.de \
    --cc=agraf@suse.com \
    --cc=axboe@fb.com \
    --cc=hare@suse.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