From: <dan.j.williams@intel.com>
To: Alison Schofield <alison.schofield@intel.com>,
Ira Weiny <ira.weiny@intel.com>
Cc: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
<dan.j.williams@intel.com>, <vishal.l.verma@intel.com>,
<dave.jiang@intel.com>, <nvdimm@lists.linux.dev>,
<linux-kernel@vger.kernel.org>,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH -next] nvdimm: Remove duplicate linux/slab.h header
Date: Tue, 30 Sep 2025 12:34:18 -0700 [thread overview]
Message-ID: <68dc30bacdee2_1fa2100c4@dwillia2-mobl4.notmuch> (raw)
In-Reply-To: <aNrAnhYMyvZ-farN@aschofie-mobl2.lan>
Alison Schofield wrote:
> On Mon, Sep 29, 2025 at 10:05:31AM -0500, Ira Weiny wrote:
> > Alison Schofield wrote:
> > > On Sun, Sep 28, 2025 at 09:31:10AM +0800, Jiapeng Chong wrote:
> > > > ./drivers/nvdimm/bus.c: linux/slab.h is included more than once.
> > >
> > > Hi Jiapeng,
> > >
> > > It would have been useful here to note where else slab.h was included,
> > > since it wasn't simply a duplicate #include in bus.c.
> >
> > Actually Alison this is a bug against linux-next where it was an issue
> > with Dave's patch here:
> >
> > https://lore.kernel.org/all/20250923174013.3319780-3-dave.jiang@intel.com/
>
> Ah, I see this removes the dup that the above patch added.
>
> Why not remove fs.h instead of slab.h and get a clean up and de-dup
> in one shot?
fs.h is included for 'struct file_operations', so no clean up
opportunity there. Recall the "include what you use" recommendation:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submit-checklist.rst?id=v6.17-rc7#n17
prev parent reply other threads:[~2025-09-30 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 1:31 [PATCH -next] nvdimm: Remove duplicate linux/slab.h header Jiapeng Chong
2025-09-29 1:26 ` Alison Schofield
2025-09-29 15:05 ` Ira Weiny
2025-09-29 17:23 ` Alison Schofield
2025-09-30 19:34 ` dan.j.williams [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=68dc30bacdee2_1fa2100c4@dwillia2-mobl4.notmuch \
--to=dan.j.williams@intel.com \
--cc=abaci@linux.alibaba.com \
--cc=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=vishal.l.verma@intel.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