From: Nikolay Aleksandrov <razor@blackwall.org>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, gospo@cumulusnetworks.com,
j.vosburgh@gmail.com, vfalico@gmail.com,
Nikolay Aleksandrov <razor@blackwall.org>
Subject: [PATCH net-next 0/2] bonding: extend the 3ad exported attributes
Date: Sun, 14 Jun 2015 16:36:33 +0300 [thread overview]
Message-ID: <1434288995-25457-1-git-send-email-razor@blackwall.org> (raw)
Hi,
These are two small patches that export actor_oper_port_state and
partner_oper_port_state via netlink and sysfs, until now they were only
exported via bond's proc entry. If this set gets accepted I have an iproute2
patch prepared that will export them with which I tested these changes.
Best regards,
Nikolay Aleksandrov
Nikolay Aleksandrov (2):
bonding: export slave's actor_oper_port_state via sysfs and netlink
bonding: export slave's partner_oper_port_state via sysfs and netlink
drivers/net/bonding/bond_netlink.c | 15 ++++++++++++++-
drivers/net/bonding/bond_sysfs_slave.c | 32 ++++++++++++++++++++++++++++++++
include/uapi/linux/if_link.h | 2 ++
3 files changed, 48 insertions(+), 1 deletion(-)
--
2.4.3
next reply other threads:[~2015-06-14 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-14 13:36 Nikolay Aleksandrov [this message]
2015-06-14 13:36 ` [PATCH net-next 1/2] bonding: export slave's actor_oper_port_state via sysfs and netlink Nikolay Aleksandrov
2015-06-15 14:09 ` Andy Gospodarek
2015-06-14 13:36 ` [PATCH net-next 2/2] bonding: export slave's partner_oper_port_state " Nikolay Aleksandrov
2015-06-15 14:10 ` Andy Gospodarek
2015-06-15 23:40 ` [PATCH net-next 0/2] bonding: extend the 3ad exported attributes David Miller
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=1434288995-25457-1-git-send-email-razor@blackwall.org \
--to=razor@blackwall.org \
--cc=davem@davemloft.net \
--cc=gospo@cumulusnetworks.com \
--cc=j.vosburgh@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=vfalico@gmail.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 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).