From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Flavio Leitner <fbl-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [PATCH] net: get rid of SET_ETHTOOL_OPS
Date: Wed, 02 Jul 2014 11:48:51 +0200 [thread overview]
Message-ID: <5006516.KlozUPNl4J@xps13> (raw)
In-Reply-To: <1404238780-19596-1-git-send-email-fbl-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Hi Flavio,
2014-07-01 15:19, Flavio Leitner:
> The SET_ETHTOOL_OPS has been removed from upstream, so it
> breaks the dpdk build with recent kernels.
>
> Signed-off-by: Flavio Leitner <fbl-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
You are removing SET_ETHTOOL_OPS calls.
In a previous patch, Aaro Koskinen made the choice to redefine the macro
in kcompat files.
I don't know what will be the choice of Intel in the sourceforge base driver.
So I've applied Aaro's patch as there are less modifications of the base
driver:
http://dpdk.org/browse/dpdk/commit/?id=e0b7ca0c0383411
It would be better to have patches from people working on the base driver.
So upgrades from sourceforge driver to KNI would be smoother.
Thanks
--
Thomas
next prev parent reply other threads:[~2014-07-02 9:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 18:19 [PATCH] net: get rid of SET_ETHTOOL_OPS Flavio Leitner
[not found] ` <1404238780-19596-1-git-send-email-fbl-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-07-02 9:48 ` Thomas Monjalon [this message]
2014-07-02 13:07 ` Flavio Leitner
[not found] ` <20140702130723.GU5631-xXVkluYekySzQB+pC5nmwQ@public.gmane.org>
2014-07-02 15:20 ` Thomas Monjalon
-- strict thread matches above, loose matches on Subject: below --
2014-05-08 11:53 Wilfried Klaebe
2014-05-08 11:53 ` Wilfried Klaebe
2014-05-08 11:53 ` Wilfried Klaebe
2014-05-08 13:19 ` Peter Senna Tschudin
2014-05-08 13:19 ` Peter Senna Tschudin
2014-05-08 13:19 ` Peter Senna Tschudin
2014-05-08 17:28 ` David Miller
2014-05-08 11:53 Wilfried Klaebe
2014-05-08 11:53 Wilfried Klaebe
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=5006516.KlozUPNl4J@xps13 \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=fbl-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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.