From: Jens Axboe <axboe@kernel.dk>
To: hch@lst.de, ming.lei@redhat.com, Yu Kuai <yukuai1@huaweicloud.com>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
yukuai3@huawei.com, yi.zhang@huawei.com, yangerkun@huawei.com
Subject: Re: [PATCH v4 0/2] block: warn once for each partition in bio_check_ro()
Date: Tue, 28 Nov 2023 12:11:33 -0700 [thread overview]
Message-ID: <170119869379.128043.13576945712245414307.b4-ty@kernel.dk> (raw)
In-Reply-To: <20231128123027.971610-1-yukuai1@huaweicloud.com>
On Tue, 28 Nov 2023 20:30:25 +0800, Yu Kuai wrote:
> Changes in v4:
> - remove the patch to add 'bd_flags', and add a new field 'bool
> bd_ro_warned' in patch 2. 'bd_flags' will be added once 'bd_inode' is
> removed from other thread.
>
> Changes in v3:
> - add patch 1 from Ming, swap bd_inode layout with bd_openers and
> bd_size_lock;
> - change bd_flags from u32 to u16 in patch 2, prevent to affect layout of
> other fields;
>
> [...]
Applied, thanks!
[1/2] block: move .bd_inode into 1st cacheline of block_device
commit: fad907cffd4bde7384812cf32fcf69becab805cc
[2/2] block: warn once for each partition in bio_check_ro()
commit: 67d995e069535c32829f5d368d919063492cec6e
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2023-11-28 19:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 12:30 Yu Kuai
2023-11-28 12:30 ` [PATCH v4 1/2] block: move .bd_inode into 1st cacheline of block_device Yu Kuai
2023-11-28 12:58 ` Christoph Hellwig
2023-11-28 12:30 ` [PATCH v4 2/2] block: warn once for each partition in bio_check_ro() Yu Kuai
2023-11-28 13:00 ` Christoph Hellwig
2023-11-29 1:13 ` Yu Kuai
2023-11-28 19:11 ` 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=170119869379.128043.13576945712245414307.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.com \
/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
all inboxes | Powered by JetHome®