From: John Fastabend <john.fastabend@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Denys Fedoryshchenko <nuclearcat@nuclearcat.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: HHF support in iproute2?
Date: Thu, 01 May 2014 09:21:23 -0700 [thread overview]
Message-ID: <53627483.2050507@gmail.com> (raw)
In-Reply-To: <CAOaVG153tfEqZvr3EC9Z1-Tc1ZWaQ6tVvswarYxtPzVRuQ88HA@mail.gmail.com>
On 05/01/2014 08:41 AM, Stephen Hemminger wrote:
> I find/pick up patches from patchwork.
> If it wasn't there then it didn't get picked up
>
Its in patchwork I just don't see it in the package I pulled from
git.kernel.org. I looked in the master and net-next-for-3.13 branches.
The patchwork patch is,
http://patchwork.ozlabs.org/patch/308514/
>
> On Thu, May 1, 2014 at 8:23 AM, John Fastabend <john.fastabend@gmail.com
> <mailto:john.fastabend@gmail.com>> wrote:
>
> On 04/11/2014 09:11 PM, Denys Fedoryshchenko wrote:
>
> Hi
>
> I just tried recently last iproute2 (git and release) and noticed in
> iproute-3.14.0 it is still missing HHF support, while i see it is
> accepted in git
> (http://marc.info/?l=linux-__netdev&m=138933793006411&w=2
> <http://marc.info/?l=linux-netdev&m=138933793006411&w=2>)
> Is there any problem with this scheduling discipline?
>
> Thanks!
>
>
> Hi Stephen,
>
> I can't seem to find this patch either. I checked the repository
> at git.kernel.org <http://git.kernel.org> and it looks like q_hhf.c
> is missing.
>
> Was this intentional? Or am I just missing something. I have the
> patch applied locally and it seems to work OK.
>
> Thanks,
> John
>
> --
> John Fastabend Intel Corporation
>
>
--
John Fastabend Intel Corporation
next prev parent reply other threads:[~2014-05-01 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-12 4:11 HHF support in iproute2? Denys Fedoryshchenko
2014-05-01 15:23 ` John Fastabend
[not found] ` <CAOaVG153tfEqZvr3EC9Z1-Tc1ZWaQ6tVvswarYxtPzVRuQ88HA@mail.gmail.com>
2014-05-01 16:21 ` John Fastabend [this message]
2014-05-01 16:42 ` Stephen Hemminger
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=53627483.2050507@gmail.com \
--to=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nuclearcat@nuclearcat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).