[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250714183242.58bf076f@kernel.org>
Date: Mon, 14 Jul 2025 18:32:42 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Li Tian <litian@...hat.com>
Cc: netdev@...r.kernel.org, linux-hyperv@...r.kernel.org,
linux-kernel@...r.kernel.org, Haiyang Zhang <haiyangz@...rosoft.com>,
Dexuan Cui <decui@...rosoft.com>, Stephen Hemminger
<stephen@...workplumber.org>, Long Li <longli@...rosoft.com>
Subject: Re: [PATCH net v3] hv_netvsc: Set VF priv_flags to IFF_NO_ADDRCONF
before open to prevent IPv6 addrconf
On Sat, 12 Jul 2025 18:07:08 +0800 Li Tian wrote:
> Set an additional flag IFF_NO_ADDRCONF to prevent ipv6 addrconf.
>
> Commit 8a321cf7becc
> ("net: add IFF_NO_ADDRCONF and use it in bonding to prevent ipv6 addrconf")
This line looks quite odd, it's in the middle of the commit message but
it's not a real sentence. If there's a single Fixes tag I usually refer
to it as "commit under Fixes", e.g. "Commit under Fixes changed XYZ but
it missed .." Please make this commit message read like a coherent
explanation rather than set of notes..
> This new flag change was not made to hv_netvsc resulting in the VF being
> assinged an IPv6.
>
> Fixes: 8a321cf7becc ("net: add IFF_NO_ADDRCONF and use it in bonding to prevent ipv6 addrconf")
--
pw-bot: cr
Powered by blists - more mailing lists