[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240703184143.3340207d@kernel.org>
Date: Wed, 3 Jul 2024 18:41:43 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Konstantin Taranov <kotaranov@...ux.microsoft.com>
Cc: kotaranov@...rosoft.com, pabeni@...hat.com, haiyangz@...rosoft.com,
kys@...rosoft.com, edumazet@...gle.com, davem@...emloft.net,
decui@...rosoft.com, wei.liu@...nel.org, sharmaajay@...rosoft.com,
longli@...rosoft.com, jgg@...pe.ca, leon@...nel.org,
linux-rdma@...r.kernel.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH net-next v2 0/2] Provide master netdev to mana_ib
On Mon, 1 Jul 2024 05:58:54 -0700 Konstantin Taranov wrote:
> This patch series aims to allow mana_ib to get master netdev
> from mana. In the netvsc deployment, the VF netdev is enslaved
> by netvsc and the upper device should be considered for the network
> state. In the baremetal case, the VF netdev is a master device.
>
> I would appreciate if I could get Acks on it from:
> * netvsc maintainers (e.g., Haiyang)
> * net maintainers (e.g., Jakub, David, Eric, Paolo)
Would you like us to take this via net-next?
- it doesn't apply cleanly
- the patches should be squashed, they aren't separate logical changes
- please find a better word than master
Powered by blists - more mailing lists