[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZIyv3b+Cn2m+/Oi9@x130>
Date: Fri, 16 Jun 2023 11:54:21 -0700
From: Saeed Mahameed <saeed@...nel.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Maxim Mikityanskiy <maxtram95@...il.com>, netdev@...r.kernel.org,
Saeed Mahameed <saeedm@...dia.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
Gal Pressman <gal@...dia.com>, Tariq Toukan <tariqt@...dia.com>,
bpf@...r.kernel.org
Subject: Re: [PATCH net-next v4 0/2] xdp_rxq_info_reg fixes for mlx5e
On 15 Jun 22:32, Jakub Kicinski wrote:
>On Wed, 14 Jun 2023 12:00:04 +0300 Maxim Mikityanskiy wrote:
>> Marked for net-next, as I'm not sure what the consensus was, but they
>> can be applied cleanly to net as well.
>
>Sorry for lack of clarity, you should drop the fixes tags.
>If not implementing something was a bug most of the patches we merge
>would have a fixes tag. That devalues the Fixes tag completely.
>You can still ask Greg/Sasha to backport it later if you want.
>
You don't think this should go to net ?
The first 3 version were targeting net branch .. I don't know why Maxim
decided to switch v4 to net-next, Maybe I missed an email ?
IMHO, I think these are net worthy since they are fixing
issues with blabla, for commits claiming to add support for blabla.
I already applied those earlier to my net queue and was working on
submission today, let me know if you are ok for me to send those two
patches in my today's net PR.
Thanks,
Saeed
Powered by blists - more mailing lists