DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] kni: fix build with kernel < 3.3 with netdev_features_t backport
Date: Fri, 26 Jul 2013 15:21:30 +0200	[thread overview]
Message-ID: <201307261521.30526.thomas.monjalon@6wind.com> (raw)
In-Reply-To: <1374837948-20169-1-git-send-email-adrien.mazarguil@6wind.com>

26/07/2013 13:25, Adrien Mazarguil :
> The netdev_features_t typedef appeared in Linux 3.3, but checking the
> kernel version isn't enough with some distributions (such as Debian
> Wheezy) that backported it into 3.2, causing a compilation failure due to
> redefinition.
> 
> Since the presence of a typedef can't be tested at compile time, this
> commit adds type kni_netdev_features_t, which, depending on the kernel
> version, translates either to u32 or netdev_features_t.
> 
> Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>

acked and applied

-- 
Thomas

      reply	other threads:[~2013-07-26 13:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26 11:25 Adrien Mazarguil
2013-07-26 13:21 ` 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=201307261521.30526.thomas.monjalon@6wind.com \
    --to=thomas.monjalon@6wind.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.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).