Netdev List
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Michal Kubecek <mkubecek@suse.cz>
Cc: Stephen Hemminger <stephen@networkplumber.org>, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 net-next-for-3.13 0/2] iproute2: display bonding slave info
Date: Mon, 10 Feb 2014 10:49:48 +0100	[thread overview]
Message-ID: <20140210094948.GA2785@minipsycho.orion> (raw)
In-Reply-To: <20140210081136.66C22E5697@unicorn.suse.cz>

Already queued in patchwork:

http://patchwork.ozlabs.org/patch/313656/
http://patchwork.ozlabs.org/patch/313657/


Mon, Feb 10, 2014 at 09:11:36AM CET, mkubecek@suse.cz wrote:
>Since v3.14-rc1, kernel provides rtnetlink interface for read-only
>access to bonding slave parameters. Show this info in the output of
>"ip -d link show" command. The implementation is divided into generic
>part (add a callback to struct link_util and call it from
>print_linktype()) and bonding specific part (provide the callback in
>iplink_bond.c).
>
>Michal Kubecek (2):
>  iplink: display slave information
>  iplink_bond: add support for displaying bond slave attributes
>
> ip/ip_common.h   |  3 +++
> ip/ipaddress.c   | 27 +++++++++++++++++++++++--
> ip/iplink_bond.c | 61 ++++++++++++++++++++++++++++++++++++++++++++++++++++----
> 3 files changed, 85 insertions(+), 6 deletions(-)
>
>-- 
>1.8.1.4
>
>--
>To unsubscribe from this list: send the line "unsubscribe netdev" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2014-02-10  9:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10  8:11 [PATCH iproute2 net-next-for-3.13 0/2] iproute2: display bonding slave info Michal Kubecek
2014-02-10  9:49 ` Jiri Pirko [this message]

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=20140210094948.GA2785@minipsycho.orion \
    --to=jiri@resnulli.us \
    --cc=mkubecek@suse.cz \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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