DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Xu, Rosen" <rosen.xu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
	"gaetan.rivet@6wind.com" <gaetan.rivet@6wind.com>,
	"Pei, Yulong" <yulong.pei@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc/guides/rel_notes: Add known issue for IOMMU attributes read
Date: Mon, 28 May 2018 15:31:12 +0000	[thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23F3468DE@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1526455752-147108-1-git-send-email-rosen.xu@intel.com>



> -----Original Message-----
> From: Xu, Rosen
> Sent: Wednesday, May 16, 2018 8:29 AM
> To: dev@dpdk.org
> Cc: Burakov, Anatoly <anatoly.burakov@intel.com>; gaetan.rivet@6wind.com;
> Mcnamara, John <john.mcnamara@intel.com>; Xu, Rosen <rosen.xu@intel.com>;
> Pei, Yulong <yulong.pei@intel.com>; stable@dpdk.org
> Subject: [PATCH v2] doc/guides/rel_notes: Add known issue for IOMMU
> attributes read
> 
> Linux kernel 4.10.0 iommu attribute read error
> 
> Cc: stable@dpdk.org
> 
> Signed-off-by: Rosen Xu <rosen.xu@intel.com>


Could you open an Bugzilla defect for this and add it to the text.

Like this patch: http://dpdk.org/dev/patchwork/patch/40475/

Thanks,

John

  reply	other threads:[~2018-05-28 15:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-14 10:44 [dpdk-dev] [PATCH] " Rosen Xu
2018-05-14 17:10 ` Burakov, Anatoly
2018-05-16  6:08   ` Xu, Rosen
2018-05-16  7:29 ` [dpdk-dev] [PATCH v2] " Rosen Xu
2018-05-28 15:31   ` Mcnamara, John [this message]
2018-05-28 15:36     ` Mcnamara, John
2018-05-29  0:25       ` Xu, Rosen
2018-05-30 12:04       ` [dpdk-dev] [dpdk-stable] " 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=B27915DBBA3421428155699D51E4CFE23F3468DE@IRSMSX103.ger.corp.intel.com \
    --to=john.mcnamara@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=gaetan.rivet@6wind.com \
    --cc=rosen.xu@intel.com \
    --cc=stable@dpdk.org \
    --cc=yulong.pei@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).