All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>, Minchan Kim <minchan@kernel.org>,
	dm-devel@redhat.com, linux-block@vger.kernel.org
Subject: Re: [dm-devel] misc struct block_device related driver cleanups
Date: Tue, 17 Nov 2020 11:09:59 -0500	[thread overview]
Message-ID: <20201117160958.GB27085@redhat.com> (raw)
In-Reply-To: <20201117155100.GA20977@lst.de>

On Tue, Nov 17 2020 at 10:51am -0500,
Christoph Hellwig <hch@lst.de> wrote:

> On Tue, Nov 17, 2020 at 10:46:29AM -0500, Mike Snitzer wrote:
> > On Mon, Nov 16 2020 at  4:20pm -0500,
> > Christoph Hellwig <hch@lst.de> wrote:
> > 
> > > Hi Jens, Minchan and Mike,
> > > 
> > > this series cleans up a few interactions of driver with struct
> > > block_device, in preparation for big changes to struct block_device
> > > that I plan to send soon.
> > 
> > Thanks, I've picked up 5 and 6 for 5.11.
> 
> I actually need them in Jens' for-5.11/block tree for my next series..

Ah, OK.. no problem.

I'll reply with my Acked-by:s

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel


WARNING: multiple messages have this Message-ID (diff)
From: Mike Snitzer <snitzer@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>, Minchan Kim <minchan@kernel.org>,
	dm-devel@redhat.com, linux-block@vger.kernel.org
Subject: Re: misc struct block_device related driver cleanups
Date: Tue, 17 Nov 2020 11:09:59 -0500	[thread overview]
Message-ID: <20201117160958.GB27085@redhat.com> (raw)
In-Reply-To: <20201117155100.GA20977@lst.de>

On Tue, Nov 17 2020 at 10:51am -0500,
Christoph Hellwig <hch@lst.de> wrote:

> On Tue, Nov 17, 2020 at 10:46:29AM -0500, Mike Snitzer wrote:
> > On Mon, Nov 16 2020 at  4:20pm -0500,
> > Christoph Hellwig <hch@lst.de> wrote:
> > 
> > > Hi Jens, Minchan and Mike,
> > > 
> > > this series cleans up a few interactions of driver with struct
> > > block_device, in preparation for big changes to struct block_device
> > > that I plan to send soon.
> > 
> > Thanks, I've picked up 5 and 6 for 5.11.
> 
> I actually need them in Jens' for-5.11/block tree for my next series..

Ah, OK.. no problem.

I'll reply with my Acked-by:s


  reply	other threads:[~2020-11-17 17:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-16 21:20 [dm-devel] misc struct block_device related driver cleanups Christoph Hellwig
2020-11-16 21:20 ` Christoph Hellwig
2020-11-16 21:20 ` [dm-devel] [PATCH 1/6] mtip32xx: remove the call to fsync_bdev on removal Christoph Hellwig
2020-11-16 21:20   ` Christoph Hellwig
2020-11-16 21:20 ` [dm-devel] [PATCH 2/6] zram: remove the claim mechanism Christoph Hellwig
2020-11-16 21:20   ` Christoph Hellwig
2020-11-16 21:20 ` [dm-devel] [PATCH 3/6] zram: do not call set_blocksize Christoph Hellwig
2020-11-16 21:20   ` Christoph Hellwig
2020-11-16 21:20 ` [dm-devel] [PATCH 4/6] loop: " Christoph Hellwig
2020-11-16 21:20   ` Christoph Hellwig
2020-11-16 21:20 ` [dm-devel] [PATCH 5/6] dm: simplify flush_bio initialization in __send_empty_flush Christoph Hellwig
2020-11-16 21:20   ` Christoph Hellwig
2020-11-17 16:10   ` [dm-devel] " Mike Snitzer
2020-11-17 16:10     ` Mike Snitzer
2020-11-16 21:20 ` [dm-devel] [PATCH 6/6] dm: remove the block_device reference in struct mapped_device Christoph Hellwig
2020-11-16 21:20   ` Christoph Hellwig
2020-11-17 16:11   ` [dm-devel] " Mike Snitzer
2020-11-17 16:11     ` Mike Snitzer
2020-11-17 15:46 ` [dm-devel] misc struct block_device related driver cleanups Mike Snitzer
2020-11-17 15:46   ` Mike Snitzer
2020-11-17 15:51   ` [dm-devel] " Christoph Hellwig
2020-11-17 15:51     ` Christoph Hellwig
2020-11-17 16:09     ` Mike Snitzer [this message]
2020-11-17 16:09       ` Mike Snitzer

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=20201117160958.GB27085@redhat.com \
    --to=snitzer@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=dm-devel@redhat.com \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=minchan@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 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.