From: Stephen Hemminger <stephen@networkplumber.org>
To: Yotam Gigi <yotamg@mellanox.com>
Cc: netdev@vger.kernel.org, jiri@mellanox.com, eladr@mellanox.com
Subject: Re: [PATCH iproute2/net-next 0/3] Add the tc-sample action
Date: Mon, 6 Feb 2017 14:26:20 -0800 [thread overview]
Message-ID: <20170206142620.3e640740@xeon-e3> (raw)
In-Reply-To: <1486281534-61663-1-git-send-email-yotamg@mellanox.com>
On Sun, 5 Feb 2017 09:58:51 +0200
Yotam Gigi <yotamg@mellanox.com> wrote:
> This patchset adds the tc-sample action support and the corresponding man
> page. More information about the action and its usage can be found in the
> commit message.
>
> Yotam Gigi (3):
> tc: Add support for the sample tc action
> tc: man: Add man entry for the tc-sample action
> tc: man: matchall: Update examples to include sample
>
> bash-completion/tc | 8 +-
> include/linux/tc_act/tc_sample.h | 26 ++++++
> man/man8/Makefile | 2 +-
> man/man8/tc-matchall.8 | 10 +++
> man/man8/tc-sample.8 | 125 ++++++++++++++++++++++++++
> tc/Makefile | 1 +
> tc/m_sample.c | 186 +++++++++++++++++++++++++++++++++++++++
> 7 files changed, 356 insertions(+), 2 deletions(-)
> create mode 100644 include/linux/tc_act/tc_sample.h
> create mode 100644 man/man8/tc-sample.8
> create mode 100644 tc/m_sample.c
>
Applied to net-next. I had to fix merge conflict on tc/Makefile
prev parent reply other threads:[~2017-02-06 22:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-05 7:58 [PATCH iproute2/net-next 0/3] Add the tc-sample action Yotam Gigi
2017-02-05 7:58 ` [PATCH iproute2/net-next 1/3] tc: Add support for the sample tc action Yotam Gigi
2017-02-05 18:36 ` Florian Fainelli
2017-02-05 20:22 ` Yotam Gigi
2017-02-05 20:55 ` Florian Fainelli
2017-02-06 7:38 ` Yotam Gigi
2017-02-05 7:58 ` [PATCH iproute2/net-next 2/3] tc: man: Add man entry for the tc-sample action Yotam Gigi
2017-02-05 7:58 ` [PATCH iproute2/net-next 3/3] tc: man: matchall: Update examples to include sample Yotam Gigi
2017-02-06 22:26 ` Stephen Hemminger [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=20170206142620.3e640740@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=eladr@mellanox.com \
--cc=jiri@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=yotamg@mellanox.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