From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Qiming Yang <qiming.yang@intel.com>,
dev@dpdk.org, John McNamara <john.mcnamara@intel.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add known igb_uio issue for i40e
Date: Mon, 3 Apr 2017 11:40:05 +0100 [thread overview]
Message-ID: <aa79e4b6-ccbd-a369-82c1-83b0863a5714@intel.com> (raw)
In-Reply-To: <1490606177-38274-1-git-send-email-qiming.yang@intel.com>
On 3/27/2017 10:16 AM, Qiming Yang wrote:
> 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>
> ---
> doc/guides/nics/i40e.rst | 13 +++++++++++++
Hi John,
There are three different "Known Issue" sections in documentations:
1) Known Issues document, doc/guides/rel_notes/known_issues.rst
2) Release notes, known issues section,
doc/guides/rel_notes/release_17_05.rst
3) Device specific known issues sections, doc/guides/nics/i40e.rst
This patch updates 3), what is the rule on updating those files?
Thanks,
ferruh
next prev parent reply other threads:[~2017-04-03 10:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 9:16 Qiming Yang
2017-03-30 12:08 ` Wu, Jingjing
2017-04-03 10:40 ` Ferruh Yigit [this message]
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
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=aa79e4b6-ccbd-a369-82c1-83b0863a5714@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=qiming.yang@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).