All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamal Hadi Salim <jhs@mojatatu.com>
To: Jiri Pirko <jiri@resnulli.us>, netdev@vger.kernel.org
Cc: davem@davemloft.net, pshelar@nicira.com, therbert@google.com,
	edumazet@google.com, willemb@google.com, dborkman@redhat.com,
	mst@redhat.com, fw@strlen.de, Paul.Durrant@citrix.com,
	tgraf@suug.ch
Subject: Re: [patch net-next 2/2] sched: introduce vlan action
Date: Tue, 11 Nov 2014 07:34:01 -0500	[thread overview]
Message-ID: <54620239.6010306@mojatatu.com> (raw)
In-Reply-To: <1415700789-9171-2-git-send-email-jiri@resnulli.us>

On 11/11/14 05:13, Jiri Pirko wrote:
> This tc action allows to work with vlan tagged skbs. Two supported
> sub-actions are header pop and header push.
>
> Signed-off-by: Jiri Pirko <jiri@resnulli.us>

Looks good. I am going to test it - but dont see any obvious issues I
from inspection; willing to say:

Signed-off-by: Jamal Hadi Salim <jhs@mojatatu.com>

cheers,
jamal

  reply	other threads:[~2014-11-11 12:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-11 10:13 [patch net-next 1/2] net: move vlan pop/push functions into common code Jiri Pirko
2014-11-11 10:13 ` [patch net-next 2/2] sched: introduce vlan action Jiri Pirko
2014-11-11 12:34   ` Jamal Hadi Salim [this message]
2014-11-11 22:33   ` Cong Wang
2014-11-12 12:34     ` Jiri Pirko
2014-11-12 13:03       ` Jamal Hadi Salim
2014-11-12 13:06         ` Jamal Hadi Salim
2014-11-11 23:18   ` Cong Wang
2014-11-12  7:47     ` Jiri Pirko
2014-11-12 12:27       ` Jamal Hadi Salim
2014-11-13 17:06         ` Cong Wang
2014-11-11 13:06 ` [patch net-next 1/2] net: move vlan pop/push functions into common code Eric Dumazet
2014-11-11 15:00   ` Jiri Pirko
2014-11-11 17:24 ` Pravin Shelar
2014-11-12 11:59   ` Jiri Pirko
2014-11-12 19:11     ` David Miller
2014-11-12 19:20     ` Pravin Shelar

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=54620239.6010306@mojatatu.com \
    --to=jhs@mojatatu.com \
    --cc=Paul.Durrant@citrix.com \
    --cc=davem@davemloft.net \
    --cc=dborkman@redhat.com \
    --cc=edumazet@google.com \
    --cc=fw@strlen.de \
    --cc=jiri@resnulli.us \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pshelar@nicira.com \
    --cc=tgraf@suug.ch \
    --cc=therbert@google.com \
    --cc=willemb@google.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.