From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [memnic PATCH v2] linux: fix build with kernel 3.3
Date: Fri, 21 Mar 2014 15:59:49 +0100 [thread overview]
Message-ID: <4636533.gOB8GvANiZ@xps13> (raw)
In-Reply-To: <7F861DC0615E0C47A872E6F3C5FCDDBD010824FA@BPXM14GP.gisp.nec.co.jp>
18/03/2014 23:04, Hiroshi Shimamoto :
> > Remove unused dev_ops functions.
> >
> > The API of some functions (memnic_vlan_rx_add_vid,
> > memnic_vlan_rx_kill_vid) changed starting from 3.3 kernel. Instead of
> > using a #ifdef to handle the compilation on any kernel, we can just
> > remove these functions as they are not needed.
> >
> > Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
>
> Acked-by: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
Applied.
Thank you
--
Thomas
prev parent reply other threads:[~2014-03-21 14:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 15:59 [dpdk-dev] [memnic PATCH] linux: fix build with kernel >= 3.3 Olivier Matz
2014-01-30 11:46 ` Hiroshi Shimamoto
2014-02-07 13:04 ` [dpdk-dev] [memnic PATCH v2] linux: fix build with kernel 3.3 Olivier Matz
2014-03-18 23:04 ` Hiroshi Shimamoto
2014-03-21 14:59 ` Thomas Monjalon [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=4636533.gOB8GvANiZ@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@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).