mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: 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: Mon, 29 Sep 2025 10:23:42 -0700	[thread overview]
Message-ID: <aNrAnhYMyvZ-farN@aschofie-mobl2.lan> (raw)
In-Reply-To: <68daa03bbd9a5_270161294bd@iweiny-mobl.notmuch>

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?

> 
> I'll queue this up.
> 
> Reviewed-by: Ira Weiny <ira.weiny@intel.com>
> 
> Thanks,
> Ira
> 
> > 
> > I found slab.h is also in #include <linux/fs.h>. Then I found that this
> > compiles if I remove both of those includes. It would be worthwhile to
> > check all the includes and send a new tested version of this patch that
> > does this "Remove needless #include's in bus.c"
> > 
> > BTW - I didn't check all #includes.There may be more beyond slab.h & fs.h.
> > 
> > --Alison
> > 
> > > 
> > > Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> > > Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=25516
> > > Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
> > > ---
> > >  drivers/nvdimm/bus.c | 1 -
> > >  1 file changed, 1 deletion(-)
> > > 
> > > diff --git a/drivers/nvdimm/bus.c b/drivers/nvdimm/bus.c
> > > index ad3a0493f474..87178a53ff9c 100644
> > > --- a/drivers/nvdimm/bus.c
> > > +++ b/drivers/nvdimm/bus.c
> > > @@ -13,7 +13,6 @@
> > >  #include <linux/async.h>
> > >  #include <linux/ndctl.h>
> > >  #include <linux/sched.h>
> > > -#include <linux/slab.h>
> > >  #include <linux/cpu.h>
> > >  #include <linux/fs.h>
> > >  #include <linux/io.h>
> > > -- 
> > > 2.43.5
> > > 
> > > 
> 
> 

  reply	other threads:[~2025-09-29 17:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-28  1:31 Jiapeng Chong
2025-09-29  1:26 ` Alison Schofield
2025-09-29 15:05   ` Ira Weiny
2025-09-29 17:23     ` Alison Schofield [this message]
2025-09-30 19:34       ` dan.j.williams

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=aNrAnhYMyvZ-farN@aschofie-mobl2.lan \
    --to=alison.schofield@intel.com \
    --cc=abaci@linux.alibaba.com \
    --cc=dan.j.williams@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

all inboxes | Powered by JetHome®