[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ee08333d-d39d-45c6-9e6e-6328855d3068@kili.mountain>
Date: Mon, 13 Mar 2023 11:46:57 +0300
From: Dan Carpenter <error27@...il.com>
To: Alexander Lobakin <aleksander.lobakin@...el.com>
Cc: Muhammad Usama Anjum <usama.anjum@...labora.com>,
Simon Horman <simon.horman@...igine.com>,
Jakub Kicinski <kuba@...nel.org>,
Ariel Elior <aelior@...vell.com>,
Manish Chopra <manishc@...vell.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>, kernel@...labora.com,
kernel-janitors@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] qede: remove linux/version.h and linux/compiler.h
On Tue, Mar 07, 2023 at 06:13:16PM +0100, Alexander Lobakin wrote:
> >> Also, as per the examples above, the target tree, in this case
> >> 'net-next' should be included in the subject.
> > I don't know much about net tree and its location. This is why people use
>
> Here[0].
>
> > linux-next for sending patches. I'm not sure about the networking sub
>
> No, people use the corresponding mailing lists to send and repositories
> to base their patches on.
>
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.
regards,
dan carpenter
Powered by blists - more mailing lists