Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH net-next v2] net: ipconfig: Release the rtnl_lock while
 waiting for carrier
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <163542840769.2633.15242995859268025107.git-patchwork-notify@kernel.org>
Date:   Thu, 28 Oct 2021 13:40:07 +0000
References: <20211028131804.413243-1-maxime.chevallier@bootlin.com>
In-Reply-To: <20211028131804.413243-1-maxime.chevallier@bootlin.com>
To:     Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc:     davem@davemloft.net, linux@armlinux.org.uk,
        yoshfuji@linux-ipv6.org, dsahern@kernel.org, kuba@kernel.org,
        atenart@kernel.org, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org, thomas.petazzoni@bootlin.com
Precedence: bulk

Hello:

This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Thu, 28 Oct 2021 15:18:04 +0200 you wrote:
> While waiting for a carrier to come on one of the netdevices, some
> devices will require to take the rtnl lock at some point to fully
> initialize all parts of the link.
> 
> That's the case for SFP, where the rtnl is taken when a module gets
> detected. This prevents mounting an NFS rootfs over an SFP link.
> 
> [...]

Here is the summary with links:
  - [net-next,v2] net: ipconfig: Release the rtnl_lock while waiting for carrier
    https://git.kernel.org/netdev/net-next/c/ee046d9a22a4

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html