From: sfeldma@gmail.com
To: netdev@vger.kernel.org
Cc: jiri@resnulli.us, gospo@cumulusnetworks.com
Subject: [PATCH net-next 0/4] switchdev: documentation updates
Date: Wed, 3 Jun 2015 20:43:39 -0700 [thread overview]
Message-ID: <1433389423-58467-1-git-send-email-sfeldma@gmail.com> (raw)
From: Scott Feldman <sfeldma@gmail.com>
Update the switchdev documentation to clarify that for IPV4 FIB object, the add
op is used for both adding and modifying the FIB entry on the device.
I found a few other white-space and grammer issues to fix, and to clarify the
static FDB ops.
Scott Feldman (4):
switchdev: documentation: fix longer-than-80-char lines
switchdev: documentation: fix grammer error
switchdev: documentation: for static FDB ops, use
switchdev_port_fdb_xxx ops
switchdev: documentation: use switchdev_port_obj_xxx for IPv4 FIB
add/modify/delete ops
Documentation/networking/switchdev.txt | 95 +++++++++++++++++---------------
net/switchdev/switchdev.c | 4 +-
2 files changed, 54 insertions(+), 45 deletions(-)
--
1.7.10.4
next reply other threads:[~2015-06-04 3:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 3:43 sfeldma [this message]
2015-06-04 3:43 ` [PATCH net-next 1/4] switchdev: documentation: fix longer-than-80-char lines sfeldma
2015-06-04 6:16 ` Jiri Pirko
2015-06-04 3:43 ` [PATCH net-next 2/4] switchdev: documentation: fix grammer error sfeldma
2015-06-04 6:17 ` Jiri Pirko
2015-06-04 14:14 ` Sergei Shtylyov
2015-06-04 3:43 ` [PATCH net-next 3/4] switchdev: documentation: for static FDB ops, use switchdev_port_fdb_xxx ops sfeldma
2015-06-04 6:17 ` Jiri Pirko
2015-06-04 3:43 ` [PATCH net-next 4/4] switchdev: documentation: use switchdev_port_obj_xxx for IPv4 FIB add/modify/delete ops sfeldma
2015-06-04 6:17 ` Jiri Pirko
2015-06-04 6:47 ` [PATCH net-next 0/4] switchdev: documentation updates 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=1433389423-58467-1-git-send-email-sfeldma@gmail.com \
--to=sfeldma@gmail.com \
--cc=gospo@cumulusnetworks.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).