From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>, song@kernel.org
Cc: guoqing.jiang@cloud.ionos.com, linux-block@vger.kernel.org,
linux-raid@vger.kernel.org
Subject: Re: md read-only fixes
Date: Mon, 1 Feb 2021 09:35:49 -0700 [thread overview]
Message-ID: <656b8eb7-b2a1-b6ac-5620-29cb59fe5def@kernel.dk> (raw)
In-Reply-To: <20210201131721.750412-1-hch@lst.de>
On 2/1/21 6:17 AM, Christoph Hellwig wrote:
> Hi all,
>
> patch 1 fixes a regression in md in for-5.12/block, and patch 2
> fixes a little inconsistency in the same area.
Applied, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2021-02-01 16:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 13:17 md read-only fixes Christoph Hellwig
2021-02-01 13:17 ` [PATCH 1/2] md: check for NULL ->meta_bdev before calling bdev_read_only Christoph Hellwig
2021-02-01 13:17 ` [PATCH 2/2] md: use rdev_read_only in restart_array Christoph Hellwig
2021-02-01 16:35 ` Jens Axboe [this message]
2021-02-18 9:30 ` md read-only fixes Tkaczyk, Mariusz
2021-02-24 8:45 ` Song Liu
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=656b8eb7-b2a1-b6ac-5620-29cb59fe5def@kernel.dk \
--to=axboe@kernel.dk \
--cc=guoqing.jiang@cloud.ionos.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=song@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).