From: Jakub Kicinski <kuba@kernel.org>
To: Sean Anderson <seanga2@gmail.com>
Cc: Matthew Wilcox <willy@infradead.org>,
Simon Horman <horms@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
kernel test robot <lkp@intel.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Linux Memory Management List <linux-mm@kvack.org>,
linux-m68k@lists.linux-m68k.org
Subject: Re: [PATCH net-next] net: sunhme: move asm includes to below linux includes
Date: Wed, 5 Apr 2023 16:25:14 -0700 [thread overview]
Message-ID: <20230405162514.3af0776f@kernel.org> (raw)
In-Reply-To: <ZC2/Pi+M4rWw89x2@casper.infradead.org>
On Wed, 5 Apr 2023 19:34:38 +0100 Matthew Wilcox wrote:
> On Wed, Apr 05, 2023 at 02:09:55PM -0400, Sean Anderson wrote:
> > On 4/5/23 14:07, Matthew Wilcox wrote:
> > > We always include linux/* headers before asm/*. The "sorting" of
> > > headers in this way was inappropriate.
> >
> > Is this written down anywhere? I couldn't find it in Documentation/process...
>
> Feel free to send a patch.
Patch to documentation, checkpatch or both :)
next prev parent reply other threads:[~2023-04-05 23:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 17:29 [PATCH net-next] net: sunhme: move asm includes to below linux includes Simon Horman
2023-04-05 17:34 ` Sean Anderson
2023-04-05 18:02 ` Simon Horman
2023-04-05 18:07 ` Matthew Wilcox
2023-04-05 18:09 ` Sean Anderson
2023-04-05 18:34 ` Matthew Wilcox
2023-04-05 23:25 ` Jakub Kicinski [this message]
2023-04-06 12:10 ` Geert Uytterhoeven
2023-04-07 2:10 ` patchwork-bot+netdevbpf
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=20230405162514.3af0776f@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geert@linux-m68k.org \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=seanga2@gmail.com \
--cc=willy@infradead.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.