All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamal Hadi Salim <jhs@mojatatu.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, phil@nwl.cc
Subject: Re: [iproute2 PATCH v3 1/1] tc: introduce IFE action
Date: Mon, 25 Apr 2016 08:28:24 -0400	[thread overview]
Message-ID: <571E0D68.1050106@mojatatu.com> (raw)
In-Reply-To: <20160422100047.083055ee@xeon-e3>

On 16-04-22 01:00 PM, Stephen Hemminger wrote:
> On Thu, 21 Apr 2016 17:40:14 -0400

>
> All header files for iproute2 (in include/linux) should come from santized kernel
> headers. I do not see the file tc_ife.h in include/uapi/linux in current net-next
> kernel source tree.
>

I am assuming based on your other email this is taken care of?
Let me know if you want me to do something from my side.
I have other patches which build on top of this. If you have this
one i will send the others.

cheers,
jamal

  reply	other threads:[~2016-04-25 12:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21 21:40 [iproute2 PATCH v3 1/1] tc: introduce IFE action Jamal Hadi Salim
2016-04-22 17:00 ` Stephen Hemminger
2016-04-25 12:28   ` Jamal Hadi Salim [this message]
2016-05-07 13:11     ` Jamal Hadi Salim

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=571E0D68.1050106@mojatatu.com \
    --to=jhs@mojatatu.com \
    --cc=netdev@vger.kernel.org \
    --cc=phil@nwl.cc \
    --cc=stephen@networkplumber.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 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.