From: Jonathan Toppins <jtoppins@redhat.com>
To: netdev@vger.kernel.org
Cc: jtoppins@redhat.com
Subject: [net-next 0/2] bonding: netlink errors and cleanup
Date: Mon, 6 Jun 2022 11:26:51 -0400 [thread overview]
Message-ID: <cover.1654528729.git.jtoppins@redhat.com> (raw)
The first patch attempts to set helpful error messages when
configuring bonds via netlink. The second patch removes redundant
init code for RLB mode which is already done in bond_open.
Jonathan Toppins (2):
bonding: netlink error message support for options
bonding: cleanup bond_create
drivers/net/bonding/bond_main.c | 24 ++-----
drivers/net/bonding/bond_netlink.c | 101 +++++++++++++++++++----------
drivers/net/bonding/bond_options.c | 29 +++++++--
include/net/bond_options.h | 3 +-
4 files changed, 98 insertions(+), 59 deletions(-)
--
2.27.0
next reply other threads:[~2022-06-06 15:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 15:26 Jonathan Toppins [this message]
2022-06-06 15:26 ` [net-next 1/2] bonding: netlink error message support for options Jonathan Toppins
2022-06-08 0:19 ` Jakub Kicinski
2022-06-08 0:23 ` Jonathan Toppins
2022-06-08 0:24 ` Eric Dumazet
2022-06-08 0:32 ` Jakub Kicinski
2022-06-06 15:26 ` [net-next 2/2] bonding: cleanup bond_create Jonathan Toppins
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=cover.1654528729.git.jtoppins@redhat.com \
--to=jtoppins@redhat.com \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).