From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-block@vger.kernel.org
Subject: Re: two fixup for the block_device / hd_struct merge
Date: Thu, 1 Jul 2021 10:21:44 -0600 [thread overview]
Message-ID: <a5d794b9-6ebb-1cf3-5cb0-219f1205af53@kernel.dk> (raw)
In-Reply-To: <20210701081638.246552-1-hch@lst.de>
On 7/1/21 2:16 AM, Christoph Hellwig wrote:
> Hi Jens,
>
> find two fixes for the block_device / hd_struct merge series attached.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2021-07-01 16:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 8:16 two fixup for the block_device / hd_struct merge Christoph Hellwig
2021-07-01 8:16 ` [PATCH 1/2] block: grab a device refcount in disk_uevent Christoph Hellwig
2021-07-01 8:54 ` Ming Lei
2021-07-01 9:02 ` Christoph Hellwig
2021-07-01 9:17 ` Ming Lei
2021-07-01 9:27 ` Ming Lei
2021-07-01 9:49 ` Christoph Hellwig
2021-07-01 8:16 ` [PATCH 2/2] block: remove the bdgrab in blk_drop_partitions Christoph Hellwig
2021-07-01 16:21 ` 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=a5d794b9-6ebb-1cf3-5cb0-219f1205af53@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@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;
as well as URLs for NNTP newsgroup(s).