From: Jamal Hadi Salim <jhs@mojatatu•com>
To: Stephen Hemminger <stephen@networkplumber•org>
Cc: netdev@vger•kernel.org, phil@nwl•cc, lucasb@mojatatu•com
Subject: Re: [iproute2 1/1] man: tc-ife.8: man page for ife action
Date: Mon, 2 May 2016 19:40:58 -0400 [thread overview]
Message-ID: <5727E58A.3080307@mojatatu.com> (raw)
In-Reply-To: <20160502151032.5701009e@xeon-e3>
On 16-05-02 06:10 PM, Stephen Hemminger wrote:
> On Sat, 30 Apr 2016 06:58:04 -0400
> Jamal Hadi Salim <jhs@mojatatu•com> wrote:
>
>> From: Lucas Bates <lucasb@mojatatu•com>
>>
>> Signed-off-by: Lucas Bates <lucasb@mojatatu•com>
>> Signed-off-by: Jamal Hadi Salim <jhs@mojatatu•com>
>
> Still waiting for a you to respond to my earlier suggestions about tc-ife.
>
I did respond.
> Last version I saw was expecting header in include/linux which is not in
> kernel source.
>
> ~/kernel/net-next$ ls include/uapi/linux/tc_ife.h
> ls: cannot access include/uapi/linux/tc_ife.h: No such file or directory
>
What version of net-next are you looking at? This is what i see:
linux-gits/net-next$ ls include/uapi/linux/tc_act/
Kbuild tc_csum.h tc_ife.h tc_nat.h tc_vlan.h
tc_bpf.h tc_defact.h tc_ipt.h tc_pedit.h
tc_connmark.h tc_gact.h tc_mirred.h tc_skbedit.h
> You need to get that header in right place, and get it exported correctly.
And I saw you sending a patch which tried to export everything. What
did i miss? ;-> If that didnt make i will send one just for IFE.
cheers,
jamal
PS:- I have other patches which fix a small issue with some actions
(which include ife) - but they are depending on this other one going
in.
next prev parent reply other threads:[~2016-05-02 23:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 10:58 [iproute2 1/1] man: tc-ife.8: man page for ife action Jamal Hadi Salim
2016-04-30 11:35 ` Phil Sutter
2016-05-02 22:10 ` Stephen Hemminger
2016-05-02 23:40 ` Jamal Hadi Salim [this message]
2016-05-22 16:54 ` 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=5727E58A.3080307@mojatatu.com \
--to=jhs@mojatatu$(echo .)com \
--cc=lucasb@mojatatu$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=phil@nwl$(echo .)cc \
--cc=stephen@networkplumber$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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