All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net, jhs@mojatatu.com,
	xiyou.wangcong@gmail.com, edumazet@google.com,
	alexander.h.duyck@intel.com, daniel@iogearbox.net,
	mlxsw@mellanox.com
Subject: Re: [patch iproute2/net-next] tc: add support for TRAP action
Date: Thu, 8 Jun 2017 11:03:57 -0700	[thread overview]
Message-ID: <20170608110357.588bc32c@xeon-e3> (raw)
In-Reply-To: <20170605143945.7094-1-jiri@resnulli.us>

On Mon,  5 Jun 2017 16:39:45 +0200
Jiri Pirko <jiri@resnulli.us> wrote:

> From: Jiri Pirko <jiri@mellanox.com>
> 
> Signed-off-by: Jiri Pirko <jiri@mellanox.com>

Applied to net-next

  parent reply	other threads:[~2017-06-08 18:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-05 14:38 [patch net-next 0/6] introduce trap control action to tc and offload it Jiri Pirko
2017-06-05 14:38 ` [patch net-next 1/6] net: sched: introduce a TRAP control action Jiri Pirko
2017-06-05 19:56   ` Andrew Lunn
2017-06-05 19:59     ` Jiri Pirko
2017-06-05 14:38 ` [patch net-next 2/6] net: sched: introduce helper to identify gact trap action Jiri Pirko
2017-06-05 14:38 ` [patch net-next 3/6] mlxsw: pci: Fix size of trap_id field in CQE Jiri Pirko
2017-06-05 14:38 ` [patch net-next 4/6] mlxsw: spectrum: Introduce ACL trap Jiri Pirko
2017-06-05 14:38 ` [patch net-next 5/6] acl: Introduce ACL trap action Jiri Pirko
2017-06-05 14:38 ` [patch net-next 6/6] spectrum_flower: Implement gact trap TC action offload Jiri Pirko
2017-06-05 14:39 ` [patch iproute2/net-next] tc: add support for TRAP action Jiri Pirko
2017-06-08  6:57   ` Jiri Pirko
2017-06-08 17:26   ` Jiri Benc
2017-06-08 18:41     ` Jiri Pirko
2017-06-08 18:03   ` Stephen Hemminger [this message]
2017-06-05 15:46 ` [patch net-next 0/6] introduce trap control action to tc and offload it Andrew Lunn
2017-06-05 19:43   ` Jiri Pirko
2017-06-05 19:56     ` Jiri Pirko

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=20170608110357.588bc32c@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=alexander.h.duyck@intel.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=mlxsw@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=xiyou.wangcong@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.