From: Joerg Roedel <joro@8bytes.org>
To: Ashok Raj <ashok.raj@intel.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
CQ Tang <cq.tang@intel.com>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 1/2] iommu/vt-d: Fix some macros that are incorrectly specified in intel-iommu
Date: Mon, 30 Jan 2017 16:11:39 +0100 [thread overview]
Message-ID: <20170130151139.GD28129@8bytes.org> (raw)
In-Reply-To: <1485534760-185590-1-git-send-email-ashok.raj@intel.com>
Hi Ashok,
On Fri, Jan 27, 2017 at 08:32:39AM -0800, Ashok Raj wrote:
> From: CQ Tang <cq.tang@intel.com>
>
> Some of the macros are incorrect with wrong bit-shifts resulting in picking
> the incorrect invalidation granularity. Incorrect Source-ID in extended
> devtlb invalidation caused device side errors.
>
> To: Joerg Roedel <joro@8bytes.org>
> To: David Woodhouse <dwmw2@infradead.org>
> Cc: iommu@lists.linux-foundation.org
> Cc: linux-kernel@vger.kernel.org
> Cc: stable@vger.kernel.org
> Cc: CQ Tang <cq.tang@intel.com>
> Cc: Ashok Raj <ashok.raj@intel.com>
Can you please also add valid Fixes: tags to both patches?
Thanks,
Joerg
next prev parent reply other threads:[~2017-01-30 15:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 16:32 [PATCH 1/2] iommu/vt-d: Fix some macros that are incorrectly specified in intel-iommu Ashok Raj
2017-01-27 16:32 ` [PATCH 2/2] iommu/vt-d: tylersburg isoch identity map check is done too late Ashok Raj
2017-01-30 15:11 ` Joerg Roedel [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-30 17:39 [PATCH 1/2] iommu/vt-d: Fix some macros that are incorrectly specified in intel-iommu Ashok Raj
2017-01-31 11:57 ` Joerg Roedel
2017-01-26 21:50 Ashok Raj
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=20170130151139.GD28129@8bytes.org \
--to=joro@8bytes.org \
--cc=ashok.raj@intel.com \
--cc=cq.tang@intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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).