From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Qiu, Michael" <michael.qiu@intel.com>,
Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: NPG-PRC-SW STV <npg-prc-sw.stv@intel.com>,
DPDK_SW_ENG <dpdk_sw_eng@intel.com>,
NPG-PRC-SW STV CW <npg-prc-sw.stv.cw@intel.com>,
sys_stv <sys_stv@intel.com>,
"test-report@dpdk.org" <test-report@dpdk.org>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Glynn, Michael J" <michael.j.glynn@intel.com>
Subject: Re: [dpdk-test-report] | ERROR | daily Intel builds (31/65)
Date: Tue, 8 Mar 2016 09:25:44 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE20247F51B@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <533710CFB86FA344BFBF2D6802E6028622F615CE@SHSMSX101.ccr.corp.intel.com>
> -----Original Message-----
> From: Qiu, Michael
> Sent: Tuesday, March 8, 2016 8:35 AM
> To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
> Cc: sys_stv <sys_stv@intel.com>; test-report@dpdk.org; NPG-PRC-SW STV
> <npg-prc-sw.stv@intel.com>; NPG-PRC-SW STV CW <npg-prc-
> sw.stv.cw@intel.com>; thomas.monjalon@6wind.com; Richardson, Bruce
> <bruce.richardson@intel.com>; DPDK_SW_ENG <dpdk_sw_eng@intel.com>; Glynn,
> Michael J <michael.j.glynn@intel.com>
> Subject: RE: | ERROR | daily Intel builds (31/65)
>
> Really?
>
> Which is DPDK's scope? Support kernel or support distribution?
>
The User Guide says that the minimum kernel version is:
Kernel version >= 2.6.34
http://dpdk.org/doc/guides/linux_gsg/sys_reqs.html#system-software
This was increased from 2.6.33 in the 2.2 release in response to this commit:
2e6e9e215703 ("igb_uio: use existing PCI macros")
This was discussed and agreed on the mailing list.
John
parent reply other threads:[~2016-03-08 9:25 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <533710CFB86FA344BFBF2D6802E6028622F615CE@SHSMSX101.ccr.corp.intel.com>]
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=B27915DBBA3421428155699D51E4CFE20247F51B@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dpdk_sw_eng@intel.com \
--cc=michael.j.glynn@intel.com \
--cc=michael.qiu@intel.com \
--cc=npg-prc-sw.stv.cw@intel.com \
--cc=npg-prc-sw.stv@intel.com \
--cc=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=yuanhan.liu@linux.intel.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).