From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <thomas@monjalon.net> Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 0FC5E2BDF; Wed, 30 May 2018 14:04:13 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 9E39E21AEC; Wed, 30 May 2018 08:04:12 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 30 May 2018 08:04:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=ABYLfFblCPdc8VR3d4INnYIHqo rUKy0FfgRpNIbqyQc=; b=eFZc35xT6AJdh4TS4XdTQgVZi8+TM+poDk8OuXPQe0 UGVHwvfA5kgZzOMRq4HTW/Dx6/UgERaYtY1QcsmJfFa6GCA4d6cZEYcDqAPNwUkq e2B590GLAat+JHTYzvDrVrTIieqOzb/PZSISe3lPgTU9/p5gjg4c6Meb2hOqGHiC 8= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=ABYLfF blCPdc8VR3d4INnYIHqorUKy0FfgRpNIbqyQc=; b=Ywx2lwv4deYUfRR4xbSDq8 xZ4zvwzgV2naJbJNp0RAoXipO6wjxnL7WuFEZKjyDSGZHNXUdpqS+E0SuYafAQK4 atsG+gQ6S6fnsw1YQGZTd1VB1t5v0HFkIPqXW9h++HjHTX+fPtss9j0vJ61F/AaU K4xo3stiskewJrIBx5pJN6rnqRrCjPqwtIauhzlbzWNUmzeTzYruIRlkv3cK9AZV OVfn3RcX2I4JBVh0iKNhMDMfddCbADfjkxlYCvPTpRFxkglw8vLJZpNX/jz2TuAe Ck4yuDMfVZ9Qmaz9XRkUceL7oeXMumeSWodtolEOtybeaq3JWOz2MhPO3FfGnIxw == X-ME-Proxy: <xmx:PJMOW574SQhuCkF4RlsyOQGR3CTP9K1sNyfj97ppgR_QNx8mwTjuBA> X-ME-Proxy: <xmx:PJMOW-2FezamFWhUZ1OtFvYs-LtJ1IQGyvDWineMCIqvxFY04T7lvQ> X-ME-Proxy: <xmx:PJMOW3r9DD9eFVM8vFDOHrkopgc26CKIePX3zv8NGnGmJUsHyvX7Ow> X-ME-Proxy: <xmx:PJMOW4nmnhGLC4tOUYcoZH6ONFp3Y8JCsV06K1_bAN8uM7Q8ERZqTw> X-ME-Proxy: <xmx:PJMOW5SQAkrj8-YoJlluRwRju-JWSVzTXJ58_d_EFIMgZj_O7jRCHA> X-ME-Proxy: <xmx:PJMOW4gvFU97sZtwaJGw5WXgOoy6-dNO_z_K4xpUG6jGW8pyoIbStg> X-ME-Sender: <xms:PJMOWz03dVFi_tj2Br9evzYex7wfIoUrGclEVoIrAtx6vl4Fsk4Jcg> Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 70A82E40A3; Wed, 30 May 2018 08:04:11 -0400 (EDT) From: Thomas Monjalon <thomas@monjalon.net> To: "Xu, Rosen" <rosen.xu@intel.com> Cc: stable@dpdk.org, "Mcnamara, John" <john.mcnamara@intel.com>, "dev@dpdk.org" <dev@dpdk.org>, "Burakov, Anatoly" <anatoly.burakov@intel.com>, "gaetan.rivet@6wind.com" <gaetan.rivet@6wind.com>, "Pei, Yulong" <yulong.pei@intel.com>, "Yigit, Ferruh" <ferruh.yigit@intel.com> Date: Wed, 30 May 2018 14:04:10 +0200 Message-ID: <3018530.DW7dOApKUr@xps> In-Reply-To: <B27915DBBA3421428155699D51E4CFE23F346979@IRSMSX103.ger.corp.intel.com> References: <1526294652-102665-1-git-send-email-rosen.xu@intel.com> <B27915DBBA3421428155699D51E4CFE23F3468DE@IRSMSX103.ger.corp.intel.com> <B27915DBBA3421428155699D51E4CFE23F346979@IRSMSX103.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v2] doc/guides/rel_notes: Add known issue for IOMMU attributes read X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Wed, 30 May 2018 12:04:13 -0000 > > > 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/ > > Actually, I changed my mind. This isn't quite the same as the other new, known issues, so there is no need to track it in Bugzilla or move it to the release note. > > It is okay as is. > > Acked-by: John McNamara <john.mcnamara@intel.com> Applied, thanks