From: Christoph Hellwig <hch@lst.de>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Cc: Christoph Hellwig <hch@lst.de>,
axboe@kernel.dk, linux-block@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-aio@kvack.org,
linux-kernel@vger.kernel.org, io-uring@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH] block: split out a new blk_plug.h helper
Date: Mon, 6 Jul 2026 08:45:47 +0200 [thread overview]
Message-ID: <20260706064547.GA25268@lst.de> (raw)
In-Reply-To: <8583b332-0d24-4f6f-8831-69e3aad936fd@wdc.com>
On Mon, Jul 06, 2026 at 08:38:12AM +0200, Johannes Thumshirn wrote:
> On 7/6/26 6:11 AM, Christoph Hellwig wrote:
>> diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
>> index 9213a5716f95..20cb8ed7d987 100644
>> --- a/include/linux/blkdev.h
>> +++ b/include/linux/blkdev.h
>> @@ -7,6 +7,7 @@
>> #include <linux/types.h>
>> #include <linux/blk_types.h>
>> +#include <linux/blk_plug.h>
>> #include <linux/device.h>
>> #include <linux/list.h>
>> #include <linux/llist.h>
>>
> I know it's a lot of cross subsystem churn, but wouldn't it be cleaner to
> not include blk_plug.h in blkdev.h, but patch the update the consumers? A
> quick grep shows 68 files that would need updating and some you already
> have updated.
Right now blkdev.h needs the rq_list from it. So we'd need to move
that to linux/types.h or something first, which feels a bit iffy.
And no, including blk_types.h in blk_plug.h is not a solution,
as that is still touched far too often.
next prev parent reply other threads:[~2026-07-06 6:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 4:11 [PATCH] block: split out a new blk_plug.h helper Christoph Hellwig
2026-07-06 6:38 ` Johannes Thumshirn
2026-07-06 6:45 ` Christoph Hellwig [this message]
2026-07-06 6:47 ` Johannes Thumshirn
2026-07-06 7:04 ` Damien Le Moal
2026-07-06 9:54 ` Christoph Hellwig
2026-07-06 13:09 ` Christian Brauner
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=20260706064547.GA25268@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-aio@kvack.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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.