From: Ding Tianhong <dingtianhong@huawei.com>
To: Scott Feldman <sfeldma@cumulusnetworks.com>, <vfalico@redhat.com>,
<fubar@us.ibm.com>, <andy@greyhouse.net>
Cc: <netdev@vger.kernel.org>, <roopa@cumulusnetworks.com>,
<shm@cumulusnetworks.com>
Subject: Re: [PATCH net-next v2 0/2] bonding: add slave netlink and sysfs support
Date: Fri, 17 Jan 2014 15:47:10 +0800 [thread overview]
Message-ID: <52D8DFFE.20603@huawei.com> (raw)
In-Reply-To: <20140117065316.3194.94624.stgit@monster-03.cumulusnetworks.com>
On 2014/1/17 14:57, Scott Feldman wrote:
> v2:
>
> - Address review comment from Ding (and Veacesiav): handle kobj cleanup
> if sysfs_create_file() fails when adding slave attribute nodes.
>
> v1:
>
> The following series adds bonding slave netlink and sysfs interfaces.
> Slave interfaces get a new IFLA_SLAVE set of netlink attributes, along
> with RTM_NEWLINK notification when slave's active status changes. The
> sysfs interface adds read-only nodes for slave attributes under a /slave
> dir, simliar to how bond interfaces get a /bonding dir for bonding
> attributes.
>
> ---
>
> Scott Feldman (2):
> bonding: add sysfs /slave dir for bond slave devices.
> bonding: add netlink attributes to slave link dev
>
>
> drivers/net/bonding/Makefile | 2
> drivers/net/bonding/bond_main.c | 28 ++++++
> drivers/net/bonding/bond_netlink.c | 36 ++++++++
> drivers/net/bonding/bond_procfs.c | 12 ---
> drivers/net/bonding/bond_sysfs_slave.c | 144 ++++++++++++++++++++++++++++++++
> drivers/net/bonding/bonding.h | 15 +++
> include/linux/netdevice.h | 5 +
> include/uapi/linux/if_link.h | 13 +++
> net/core/rtnetlink.c | 54 ++++++++++++
> 9 files changed, 294 insertions(+), 15 deletions(-)
> create mode 100644 drivers/net/bonding/bond_sysfs_slave.c
>
Reviewed-by: Ding Tianhong <dingtianhong@huawei.com>
next prev parent reply other threads:[~2014-01-17 7:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 6:57 [PATCH net-next v2 0/2] bonding: add slave netlink and sysfs support Scott Feldman
2014-01-17 7:47 ` Ding Tianhong [this message]
2014-01-18 2:53 ` 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=52D8DFFE.20603@huawei.com \
--to=dingtianhong@huawei.com \
--cc=andy@greyhouse.net \
--cc=fubar@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=sfeldma@cumulusnetworks.com \
--cc=shm@cumulusnetworks.com \
--cc=vfalico@redhat.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).