[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250619152251.5005d727@kernel.org>
Date: Thu, 19 Jun 2025 15:22:51 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Saeed Mahameed <saeed@...nel.org>
Cc: Mark Bloch <mbloch@...dia.com>, "David S. Miller" <davem@...emloft.net>,
Paolo Abeni <pabeni@...hat.com>, Eric Dumazet <edumazet@...gle.com>, Andrew
Lunn <andrew+netdev@...n.ch>, Simon Horman <horms@...nel.org>,
saeedm@...dia.com, gal@...dia.com, leonro@...dia.com, tariqt@...dia.com,
Leon Romanovsky <leon@...nel.org>, Jonathan Corbet <corbet@....net>,
netdev@...r.kernel.org, linux-rdma@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 0/5] net/mlx5e: Add support for PCIe congestion
events
On Thu, 19 Jun 2025 12:19:20 -0700 Saeed Mahameed wrote:
> I think what Mark did here is fine, Yes I understand this is not
> applicable to net-next yet,
Yes, once again netdev is the problem.
> but the point is review and we can do the following, when review is done:
>
> I can Apply the mlx5-next portion to mlx5-next and Mark on V2 can send the
> net-next stuff + A PR request to the mlx5-next branch, this is how we used
> to do it all the time, but this time review happens all at once for both
> trees.
>
> Jakub is this acceptable ?
Don't complicate it, please. Send a PR with the interface patches and
we can review the rest.
Powered by blists - more mailing lists