From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: David Marchand <david.marchand@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] kni: fix build for debian kernel 3.2
Date: Wed, 30 Apr 2014 01:39:12 +0200 [thread overview]
Message-ID: <17728233.4kuYkZQCef@xps13> (raw)
In-Reply-To: <20140429142344.GB14945@hmsreliant.think-freely.org>
2014-04-29 10:23, Neil Horman:
> On Tue, Apr 29, 2014 at 04:16:03PM +0200, David Marchand wrote:
> > Following debian kernel headers upgrade to 3.2.57-3, pci capability
> > accessors have been backported (upstream commit
> > 8c0d3a02c1309eb6112d2e7c8172e8ceb26ecfca, ("PCI: Add accessors for PCI
> > Express Capability", v3.7-rc1)).
> >
> > It results in the same compilation error as redhat 6.x.
> > However, there is no clear way to determine we are building on a debian
> > kernel. So, rather than determine if we are building on a distribution
> > kernel, look at PCI_EXP_LNKSTA2 that appeared in this upstream commit.
> >
> > Signed-off-by: David Marchand <david.marchand@6wind.com>
>
> Acked-by: Neil Horman <nhorman@tuxdriver.com>
Applied for version 1.6.0r2.
Thanks
--
Thomas
prev parent reply other threads:[~2014-04-29 23:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 14:16 David Marchand
2014-04-29 14:23 ` Neil Horman
2014-04-29 23:39 ` 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=17728233.4kuYkZQCef@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=david.marchand@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).