From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org, Stephen Hemminger <shemming@brocade.com>
Subject: Re: [dpdk-dev] [PATCH] kni: fix build with Linux kernel 4.1 or later
Date: Fri, 10 Jul 2015 10:25:51 -0700 [thread overview]
Message-ID: <20150710102551.4e998ab5@urahara> (raw)
In-Reply-To: <9514159.N7eeHKzaoJ@xps13>
On Fri, 10 Jul 2015 02:53:51 +0200
Thomas Monjalon <thomas.monjalon@6wind.com> wrote:
> 2015-07-09 10:43, Stephen Hemminger:
> > From: Stephen Hemminger <shemming@brocade.com>
> >
> > The internal API for some functions used by KNI changes in current
> > kernel. KNI really needs to be submitted upstream (by Intel)
> > to keep it maintainable.
> >
> > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>
> There was already a similar patchset from Miguel Bernal Marin waiting for review:
> http://dpdk.org/dev/patchwork/patch/5862
> http://dpdk.org/dev/patchwork/patch/5863
> http://dpdk.org/dev/patchwork/patch/5864
Sure Intel patch is cleaner.
But KNI, is heading down an #ifdef rathole.
prev parent reply other threads:[~2015-07-10 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 17:43 Stephen Hemminger
2015-07-10 0:53 ` Thomas Monjalon
2015-07-10 7:16 ` De Lara Guarch, Pablo
2015-07-10 8:00 ` Thomas Monjalon
2015-07-10 17:25 ` Stephen Hemminger [this message]
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=20150710102551.4e998ab5@urahara \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=shemming@brocade.com \
--cc=thomas.monjalon@6wind.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 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).