[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 2 Feb 2021 17:54:09 +0200
From: Leon Romanovsky <leon@...nel.org>
To: Eric Dumazet <edumazet@...gle.com>
Cc: Jakub Kicinski <kuba@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Pablo Neira Ayuso <pablo@...filter.org>,
coreteam@...filter.org, Florian Westphal <fw@...len.de>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
Jozsef Kadlecsik <kadlec@...filter.org>,
Julian Anastasov <ja@....bg>,
LKML <linux-kernel@...r.kernel.org>, lvs-devel@...r.kernel.org,
Matteo Croce <mcroce@...hat.com>,
netdev <netdev@...r.kernel.org>, netfilter-devel@...r.kernel.org,
Simon Horman <horms@...ge.net.au>
Subject: Re: [PATCH net 0/4] Fix W=1 compilation warnings in net/* folder
On Tue, Feb 02, 2021 at 03:59:38PM +0100, Eric Dumazet wrote:
> On Tue, Feb 2, 2021 at 3:57 PM Leon Romanovsky <leon@...nel.org> wrote:
> >
> > On Tue, Feb 02, 2021 at 03:34:37PM +0100, Eric Dumazet wrote:
> > > On Tue, Feb 2, 2021 at 2:55 PM Leon Romanovsky <leon@...nel.org> wrote:
> > > >
> > > > From: Leon Romanovsky <leonro@...dia.com>
> > > >
> > > > Hi,
> > > >
> > > > This short series fixes W=1 compilation warnings which I experienced
> > > > when tried to compile net/* folder.
> > > >
> > >
> > > Ok, but we never had a strong requirement about W=1, so adding Fixes:
> > > tag is adding
> >
> > I added because Jakub has checker that looks for Fixes lines in "net"
> > patches.
>
> Send this to net-next
No problem.
>
> As I stated, we never enforce W=1 compilation rule.
>
> I understand we might want that for _future_ kernels.
>
> >
> > > unnecessary burden to stable teams all around the world.
> >
> > It is automatic.
>
> I do receive a copy of all backports in my mailbox, whenever I am tagged.
>
> I can tell you there is a lot of pollution.
I'm receiving them either.
>
> >
> > Thanks
Powered by blists - more mailing lists