[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250318235208.57089-1-kuniyu@amazon.com>
Date: Tue, 18 Mar 2025 16:50:00 -0700
From: Kuniyuki Iwashima <kuniyu@...zon.com>
To: <jdamato@...tly.com>
CC: <davem@...emloft.net>, <edumazet@...gle.com>, <horms@...nel.org>,
<kuba@...nel.org>, <kuni1840@...il.com>, <kuniyu@...zon.com>,
<netdev@...r.kernel.org>, <pabeni@...hat.com>
Subject: Re: [PATCH v1 net-next 1/4] af_unix: Sort headers.
From: Joe Damato <jdamato@...tly.com>
Date: Tue, 18 Mar 2025 16:07:47 -0700
> > +#include <linux/in.h>
> > #include <linux/init.h>
> > +#include <linux/kernel.h>
> > +#include <linux/module.h>
> > +#include <linux/mount.h>
> > +#include <linux/namei.h>
> > +#include <linux/net.h>
> > +#include <linux/netdevice.h>
> > #include <linux/poll.h>
> > +#include <linux/proc_fs.h>
> > #include <linux/rtnetlink.h>
> > -#include <linux/mount.h>
> > -#include <net/checksum.h>
> > +#include <linux/sched/signal.h>
>
> Not sure what the sorting rules are, but I was wondering if maybe
> "linux/sched/*.h" should come after linux/*.h and not sorted within
> linux/s*.h ?
It's simply sorted in the alphabetial order.
Actually I haven't cared about the / level, so I grepped the
linux/sched/signal.h users and it looks like most didn't care.
grep -rnI --include=*.c --include=*.h "linux/sched/signal.h" -C 3
Thanks!
Powered by blists - more mailing lists