From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>,
"Yang, Qiming" <qiming.yang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Wu, Jingjing" <jingjing.wu@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: add known igb_uio issue for i40e
Date: Fri, 14 Apr 2017 17:53:29 +0100 [thread overview]
Message-ID: <161c497c-5824-caf1-8683-fa2c03b1108f@intel.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2332BA966@IRSMSX103.ger.corp.intel.com>
On 4/14/2017 5:03 PM, Mcnamara, John wrote:
>
>
>> -----Original Message-----
>> From: Yang, Qiming
>> Sent: Thursday, April 13, 2017 4:09 AM
>> To: dev@dpdk.org
>> Cc: Wu, Jingjing <jingjing.wu@intel.com>; Mcnamara, John
>> <john.mcnamara@intel.com>; Yang, Qiming <qiming.yang@intel.com>
>> Subject: [PATCH v2] doc: add known igb_uio issue for i40e
>>
>> When insmod "igb_uio" with "intr_mode=legacy and test link status
>> interrupt. Since INTx interrupt is not supported by X710/XL710/XXV710, it
>> will cause Input/Output error when reading file descriptor.
>>
>> Signed-off-by: Qiming Yang <qiming.yang@intel.com> Acked-by Jingjing Wu
>> <jingjing.wu@intel.com>
>
> Acked-by: John McNamara <john.mcnamara@intel.com>
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2017-04-14 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 9:16 [dpdk-dev] [PATCH] " Qiming Yang
2017-03-30 12:08 ` Wu, Jingjing
2017-04-03 10:40 ` Ferruh Yigit
2017-04-03 13:30 ` Mcnamara, John
2017-04-13 3:08 ` [dpdk-dev] [PATCH v2] " Qiming Yang
2017-04-14 16:03 ` Mcnamara, John
2017-04-14 16:53 ` Ferruh Yigit [this message]
2017-04-19 4:16 ` [dpdk-dev] [PATCH v3] " Qiming Yang
2017-04-19 10:06 ` Ferruh Yigit
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=161c497c-5824-caf1-8683-fa2c03b1108f@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=john.mcnamara@intel.com \
--cc=qiming.yang@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).