From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
David Marchand <david.marchand@6wind.com>
Subject: Re: [dpdk-dev] [PATCH] igb_uio: use existing PCI macros
Date: Fri, 11 Sep 2015 08:31:54 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE202339402@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <2640256.iR0jT46UN8@xps13>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Friday, September 11, 2015 9:11 AM
> To: dev@dpdk.org; Yigit, Ferruh; David Marchand
> Subject: Re: [dpdk-dev] [PATCH] igb_uio: use existing PCI macros
>
> 2015-09-10 20:33, Ferruh Yigit:
> > > On Thu, Sep 10, 2015 at 6:01 PM, Ferruh Yigit
> > > <ferruh.yigit@intel.com>
> > > wrote:
> > >
> > Correct, those macros available after kernel version >= 2.6.34.
> > ...
>
> Why should we support kernel older than 2.6.34?
> Do we need to update doc/guides/rel_notes/supported_os.rst?
If we do then we should update he Linux Getting Started guide which says:
Required:
Kernel version >= 2.6.33
http://dpdk.org/doc/guides/linux_gsg/sys_reqs.html#system-software
And probably drop the section below itabout patching older kernels.
John.
--
next prev parent reply other threads:[~2015-09-11 8:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 16:01 Ferruh Yigit
2015-09-10 16:33 ` David Marchand
2015-09-10 19:33 ` Ferruh Yigit
2015-09-11 8:10 ` Thomas Monjalon
2015-09-11 8:31 ` Mcnamara, John [this message]
2015-10-25 17:51 ` Thomas Monjalon
2015-11-24 22:03 ` Thomas Monjalon
2015-11-24 22:02 ` Thomas Monjalon
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=B27915DBBA3421428155699D51E4CFE202339402@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).