From: Vlad Yasevich <vyasevic@redhat.com>
To: netdev@vger.kernel.org
Cc: shemminger@vyatta.com, john.r.fastabend@intel.com
Subject: [PATCH iproute2 0/2] Add support for bridge port link information
Date: Wed, 13 Mar 2013 16:36:32 -0400 [thread overview]
Message-ID: <1363206994-18599-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.
Vlad Yasevich (2):
bridge: Add support for setting bridge port attributes
bridge: Add support for printing bridge port attributes
bridge/br_common.h | 1 +
bridge/bridge.c | 3 +-
bridge/link.c | 289 ++++++++++++++++++++++++++++++++++++++++++++++++-
include/libnetlink.h | 2 +
lib/libnetlink.c | 13 ++-
5 files changed, 299 insertions(+), 9 deletions(-)
--
1.7.7.6
next reply other threads:[~2013-03-13 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 20:36 Vlad Yasevich [this message]
2013-03-13 20:36 ` [PATCH iproute2 1/2] bridge: Add support for setting bridge port attributes Vlad Yasevich
2013-03-13 20:36 ` [PATCH iproute2 2/2] bridge: Add support for printing " Vlad Yasevich
2013-03-14 18:49 ` [PATCH iproute2 0/2] Add support for bridge port link information 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=1363206994-18599-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).