From: Jakub Kicinski <kuba@kernel.org>
To: David J Wilder <wilder@us.ibm.com>
Cc: netdev@vger.kernel.org, jv@jvosburgh.net,
pradeeps@linux.vnet.ibm.com, pradeep@us.ibm.com,
i.maximets@ovn.org, amorenoz@redhat.com, haliu@redhat.com
Subject: Re: [PATCH net-next v1 2/2] bonding: Extend arp_ip_target format to allow for a list of vlan tags.
Date: Fri, 9 May 2025 17:42:37 -0700 [thread overview]
Message-ID: <20250509174237.6e297577@kernel.org> (raw)
In-Reply-To: <20250508183014.2554525-3-wilder@us.ibm.com>
On Thu, 8 May 2025 11:29:29 -0700 David J Wilder wrote:
> This change extends the "arp_ip_target" parameter format to allow for a
> list of vlan tags to be included for each arp target. This new list of
> tags is optional and may be omitted to preserve the current format and
> process of gathering tags. When provided the list of tags circumvents
> the process of gathering tags by using the supplied list. An empty list
> can be provided to simply skip the process of gathering tags.
drivers/net/bonding/bond_main.c:6126:55: warning: Using plain integer as NULL pointer
drivers/net/bonding/bond_main.c:6159: warning: No description found for return value of 'arp_ip_target_opt_parse'
--
pw-bot: cr
next prev parent reply other threads:[~2025-05-10 0:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 18:29 [PATCH net-next v1 0/2] bonding: Extend arp_ip_target format to allow for a list of vlan tags David J Wilder
2025-05-08 18:29 ` [PATCH net-next v1 1/2] bonding: Adding struct arp_target David J Wilder
2025-05-10 13:16 ` Jay Vosburgh
2025-05-08 18:29 ` [PATCH net-next v1 2/2] bonding: Extend arp_ip_target format to allow for a list of vlan tags David J Wilder
2025-05-10 0:42 ` Jakub Kicinski [this message]
2025-05-10 21:06 ` kernel test robot
2025-05-12 4:20 ` [PATCH net-next v1 0/2] " Hangbin Liu
2025-05-12 23:54 ` David Wilder
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=20250509174237.6e297577@kernel.org \
--to=kuba@kernel.org \
--cc=amorenoz@redhat.com \
--cc=haliu@redhat.com \
--cc=i.maximets@ovn.org \
--cc=jv@jvosburgh.net \
--cc=netdev@vger.kernel.org \
--cc=pradeep@us.ibm.com \
--cc=pradeeps@linux.vnet.ibm.com \
--cc=wilder@us.ibm.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.