Received-SPF: pass (google.com: domain of linux-kernel+bounces-135235-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH net-next v4] net: usb: ax88179_178a: non necessary second
 random mac address
From: patchwork-bot+netdevbpf@kernel.org
Message-Id: 
 <171257342742.21044.16835809046426475701.git-patchwork-notify@kernel.org>
Date: Mon, 08 Apr 2024 10:50:27 +0000
References: <20240405082431.8329-1-jtornosm@redhat.com>
In-Reply-To: <20240405082431.8329-1-jtornosm@redhat.com>
To: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
Cc: kuba@kernel.org, davem@davemloft.net, edumazet@google.com,
 horms@kernel.org, linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
 netdev@vger.kernel.org, pabeni@redhat.com

Hello:

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

On Fri,  5 Apr 2024 10:24:31 +0200 you wrote:
> If the mac address can not be read from the device registers or the
> devicetree, a random address is generated, but this was already done from
> usbnet_probe, so it is not necessary to call eth_hw_addr_random from here
> again to generate another random address.
> 
> Indeed, when reset was also executed from bind, generate another random mac
> address invalidated the check from usbnet_probe to configure if the assigned
> mac address for the interface was random or not, because it is comparing
> with the initial generated random address. Now, with only a reset from open
> operation, it is just a harmless simplification.
> 
> [...]

Here is the summary with links:
  - [net-next,v4] net: usb: ax88179_178a: non necessary second random mac address
    https://git.kernel.org/netdev/net-next/c/7c7be68346b9

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