From: Jakub Kicinski <kuba@kernel.org>
To: Dan Carpenter <error27@gmail.com>
Cc: Alexander Lobakin <aleksander.lobakin@intel.com>,
Muhammad Usama Anjum <usama.anjum@collabora.com>,
Simon Horman <simon.horman@corigine.com>,
Ariel Elior <aelior@marvell.com>,
Manish Chopra <manishc@marvell.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
kernel@collabora.com, kernel-janitors@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] qede: remove linux/version.h and linux/compiler.h
Date: Mon, 13 Mar 2023 11:45:38 -0700 [thread overview]
Message-ID: <20230313114538.74e6caca@kernel.org> (raw)
In-Reply-To: <ee08333d-d39d-45c6-9e6e-6328855d3068@kili.mountain>
On Mon, 13 Mar 2023 11:46:57 +0300 Dan Carpenter wrote:
> This is only for networking.
>
> It affect BPF too, I suppose, but I always tell everyone to just send
> BPF bug reports instead of patches. I can keep track of linux-next, net
> and net-next. No one can keep track of all @#$@#$@#$@# 300+ trees.
>
> I really hate this networking requirement but I try really hard to get
> it right and still mess up half the time.
Don't worry about it too much, there needs to be a level of
understanding for cross-tree folks. This unfortunately may
not be afforded to less known developers.. because we don't
know them/that they are working cross-tree.
Reality check for me - this is really something that should
be handled by our process scripts, right? get_maintainer/
/checkpatch ? Or that's not a fair expectation.
next prev parent reply other threads:[~2023-03-13 18:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 18:53 [PATCH v2] qede: remove linux/version.h and linux/compiler.h Muhammad Usama Anjum
2023-03-03 23:54 ` Jakub Kicinski
2023-03-07 13:39 ` Muhammad Usama Anjum
2023-03-07 16:38 ` Simon Horman
2023-03-07 16:53 ` Muhammad Usama Anjum
2023-03-07 17:13 ` Alexander Lobakin
2023-03-13 8:46 ` Dan Carpenter
2023-03-13 18:45 ` Jakub Kicinski [this message]
2023-03-14 11:13 ` Simon Horman
2023-03-15 8:01 ` Dan Carpenter
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=20230313114538.74e6caca@kernel.org \
--to=kuba@kernel.org \
--cc=aelior@marvell.com \
--cc=aleksander.lobakin@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=error27@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manishc@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.com \
--cc=usama.anjum@collabora.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;
as well as URLs for NNTP newsgroup(s).