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: [PATCH 5/6] dm: simplify flush_bio initialization in __send_empty_flush
Date: Tue, 17 Nov 2020 11:10:59 -0500 [thread overview]
Message-ID: <20201117161059.GA27209@redhat.com> (raw)
In-Reply-To: <20201116212020.1099154-6-hch@lst.de>
On Mon, Nov 16 2020 at 4:20pm -0500,
Christoph Hellwig <hch@lst.de> wrote:
> We don't really need the struct block_device to initialize a bio. So
> switch from using bio_set_dev to manually setting up bi_disk (bi_partno
> will always be zero and has been cleared by bio_init already).
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Acked-by: Mike Snitzer <snitzer@redhat.com>
next prev parent reply other threads:[~2020-11-17 16:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 21:20 misc struct block_device related driver cleanups Christoph Hellwig
2020-11-16 21:20 ` [PATCH 1/6] mtip32xx: remove the call to fsync_bdev on removal Christoph Hellwig
2020-11-16 21:20 ` [PATCH 2/6] zram: remove the claim mechanism Christoph Hellwig
2020-11-16 21:20 ` [PATCH 3/6] zram: do not call set_blocksize Christoph Hellwig
2020-11-16 21:20 ` [PATCH 4/6] loop: " Christoph Hellwig
2020-11-16 21:20 ` [PATCH 5/6] dm: simplify flush_bio initialization in __send_empty_flush Christoph Hellwig
2020-11-17 16:10 ` Mike Snitzer [this message]
2020-11-16 21:20 ` [PATCH 6/6] dm: remove the block_device reference in struct mapped_device Christoph Hellwig
2020-11-17 16:11 ` Mike Snitzer
2020-11-17 15:46 ` misc struct block_device related driver cleanups Mike Snitzer
2020-11-17 15:51 ` Christoph Hellwig
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=20201117161059.GA27209@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 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).