netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vlad Yasevich <vyasevic@redhat.com>
To: netdev@vger.kernel.org
Cc: shemminger@vyatta.com, john.r.fastabend@intel.com
Subject: [PATCHv3 iproute2 0/3] Add support for bridge port link information
Date: Fri, 15 Mar 2013 13:01:06 -0400	[thread overview]
Message-ID: <1363366869-27778-1-git-send-email-vyasevic@redhat.com> (raw)

Bridge ports provide unique link information about the properties and flags of
the port.  This patch set allows bridge utility to configure and disaplay
this information.

Please take a look at the man page text and let me know if you have anything
to add.

Since v2:
 - Remove master and self flags from brind link man page.  They were removed
   from the patch and made implicit since the only self command we support is
   hwmode right now.

Since v1:
 - Change the link output to match link command line options as suggested by
   Stephen.
 - Add man page text.
 - Add root_block attribute.

Vlad Yasevich (3):
  bridge: Add support for setting bridge port attributes
  bridge: Add support for printing bridge port attributes
  man: Add documentation for the bridge link operation.

 bridge/br_common.h   |    1 +
 bridge/bridge.c      |    3 +-
 bridge/link.c        |  294 ++++++++++++++++++++++++++++++++++++++++++++++++-
 include/libnetlink.h |    2 +
 lib/libnetlink.c     |   13 ++-
 man/man8/bridge.8    |  136 +++++++++++++++++++++---
 6 files changed, 427 insertions(+), 22 deletions(-)

-- 
1.7.7.6

             reply	other threads:[~2013-03-15 17:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-15 17:01 Vlad Yasevich [this message]
2013-03-15 17:01 ` [PATCHv3 iproute2 1/3] bridge: Add support for setting bridge port attributes Vlad Yasevich
2013-03-15 17:01 ` [PATCHv3 iproute2 2/3] bridge: Add support for printing " Vlad Yasevich
2013-03-15 17:01 ` [PATCHv3 iproute2 3/3] man: Add documentation for the bridge link operation Vlad Yasevich
2013-03-15 17:04   ` Vlad Yasevich

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=1363366869-27778-1-git-send-email-vyasevic@redhat.com \
    --to=vyasevic@redhat.com \
    --cc=john.r.fastabend@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.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).