From: Phil Sutter <phil@nwl.cc>
To: Stephen Hemminger <shemming@brocade.com>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>, netdev@vger.kernel.org
Subject: [iproute PATCH v2 0/4] tc: pedit: further fixes
Date: Tue, 22 Mar 2016 15:16:20 +0100 [thread overview]
Message-ID: <1458656184-22154-1-git-send-email-phil@nwl.cc> (raw)
The following series was created after testing pedit on a big-endian
system. It starts with a minor patch fixing coding style in tc/p_ip.c,
then the actual big-endian fixup, a fix for raw op discovered when
writing the pedit test for testsuite and finally a testsuite addon to
verify pedit functionality.
Changes since v1:
- Rebased whole series onto current master branch.
- Replaced patch 1/4 with a smaller one containing only the rebase
leftovers.
Phil Sutter (4):
tc/p_ip.c: Minor coding style cleanup
tc: pedit: Fix for big-endian systems
tc: pedit: Fix raw op
testsuite: add a test for tc pedit action
tc/m_pedit.c | 23 ++---
tc/p_ip.c | 8 +-
testsuite/tests/tc/pedit.t | 217 +++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 235 insertions(+), 13 deletions(-)
create mode 100755 testsuite/tests/tc/pedit.t
--
2.7.2
next reply other threads:[~2016-03-22 14:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 14:16 Phil Sutter [this message]
2016-03-22 14:16 ` [iproute PATCH v2 1/4] tc/p_ip.c: Minor coding style cleanup Phil Sutter
2016-03-22 14:16 ` [iproute PATCH v2 2/4] tc: pedit: Fix for big-endian systems Phil Sutter
2016-03-22 14:16 ` [iproute PATCH v2 3/4] tc: pedit: Fix raw op Phil Sutter
2016-03-22 14:16 ` [iproute PATCH v2 4/4] testsuite: add a test for tc pedit action Phil Sutter
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=1458656184-22154-1-git-send-email-phil@nwl.cc \
--to=phil@nwl.cc \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=shemming@brocade.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