From: David Ahern <dsahern@gmail.com>
To: Tonghao Zhang <tonghao@bamaicloud.com>
Cc: netdev@vger.kernel.org, Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH RESEND iproute2-next] ip/bond: add broadcast_neighbor support
Date: Mon, 22 Sep 2025 17:09:37 -0600 [thread overview]
Message-ID: <25ea5933-e917-4852-8744-6351d45f9824@gmail.com> (raw)
In-Reply-To: <9DB0492E-33D8-4478-B228-CAE5AEAC2D2C@bamaicloud.com>
On 9/19/25 3:01 AM, Tonghao Zhang wrote:
>
>
>> 2025年9月18日 10:45，David Ahern <dsahern@gmail.com> 写道：
>>
>> On 9/14/25 1:06 AM, Tonghao Zhang wrote:
>>> This option has no effect in modes other than 802.3ad mode.
>>> When this option enabled, the bond device will broadcast ARP/ND
>>> packets to all active slaves.
>>>
>>> Cc: Stephen Hemminger <stephen@networkplumber.org>
>>> Cc: David Ahern <dsahern@gmail.com>
>>> Signed-off-by: Tonghao Zhang <tonghao@bamaicloud.com>
>>> ---
>>> 1. no update uapi header. https://marc.info/?l=linux-netdev&m=170614774224160&w=3
>>> 2. the kernel patch is accpted, https://patchwork.kernel.org/project/netdevbpf/patch/84d0a044514157bb856a10b6d03a1028c4883561.1751031306.git.tonghao@bamaicloud.com/
>>> ---
>>> ip/iplink_bond.c | 16 ++++++++++++++++
>>
>> you need to update man/man8/ip-link.8.in under the bond section.
>>
> No option descriptions as follows were found in manpage. There is only a description of bond_slave. I don’t know where to update.
>
ok, looks like we are missing documentation for bond arguments.
repost your patch; no sense holding it up given the current
documentation hole.
prev parent reply other threads:[~2025-09-22 23:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-14 7:06 [PATCH RESEND iproute2-next] ip/bond: add broadcast_neighbor support Tonghao Zhang
2025-09-18 2:45 ` David Ahern
2025-09-19 9:01 ` Tonghao Zhang
2025-09-22 23:09 ` David Ahern [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=25ea5933-e917-4852-8744-6351d45f9824@gmail.com \
--to=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=tonghao@bamaicloud.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.