netdev - [patch net-next 0/5] fix bonding slave info API (sysfs and netlink)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1390377957-31466-1-git-send-email-jiri@resnulli.us>
Date:	Wed, 22 Jan 2014 09:05:52 +0100
From:	Jiri Pirko <jiri@...nulli.us>
To:	netdev@...r.kernel.org
Cc:	davem@...emloft.net, fubar@...ibm.com, vfalico@...hat.com,
	andy@...yhouse.net, sfeldma@...ulusnetworks.com,
	stephen@...workplumber.org, vyasevic@...hat.com,
	nicolas.dichtel@...nd.com, john.r.fastabend@...el.com
Subject: [patch net-next 0/5] fix bonding slave info API (sysfs and netlink)

The main part of this patchset is the introduction of a generic way how
to get/set info of slaves unsing rtnl_link_ops.

Jiri Pirko (5):
  bonding: change name of sysfs dir for bonding slaves
  rtnetlink: put "BOND" into nl attribute names which are related to
    bonding
  rtnetlink: provide api for getting and setting slave info
  bonding: convert netlink to use slave data info api
  rtnetlink: remove ndo_get_slave

 drivers/net/bonding/bond_main.c        |   1 -
 drivers/net/bonding/bond_netlink.c     |  33 ++++--
 drivers/net/bonding/bond_sysfs_slave.c |   2 +-
 drivers/net/bonding/bonding.h          |   1 -
 include/linux/netdevice.h              |   5 -
 include/net/rtnetlink.h                |  14 +++
 include/uapi/linux/if_link.h           |  21 ++--
 net/core/rtnetlink.c                   | 209 ++++++++++++++++++++++-----------
 8 files changed, 190 insertions(+), 96 deletions(-)

-- 
1.8.3.1

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html