From: Joerg Roedel <joro@8bytes.org>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: dwmw2@infradead.org, ashok.raj@intel.com,
jacob.jun.pan@linux.intel.com, jisben@google.com,
xmdong@google.com, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, Fenghua Yu <fenghua.yu@intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 1/1] iommu/vt-d: Check identity map for hot-added devices
Date: Tue, 26 Feb 2019 11:56:07 +0100 [thread overview]
Message-ID: <20190226105607.GI20740@8bytes.org> (raw)
In-Reply-To: <20190225024636.32418-1-baolu.lu@linux.intel.com>
On Mon, Feb 25, 2019 at 10:46:36AM +0800, Lu Baolu wrote:
> drivers/iommu/intel-iommu.c | 21 ++++++++++++---------
> 1 file changed, 12 insertions(+), 9 deletions(-)
Added a Fixes: tag and applied the patch, thanks.
prev parent reply other threads:[~2019-02-26 10:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 2:46 [PATCH 1/1] iommu/vt-d: Check identity map for hot-added devices Lu Baolu
2019-02-26 10:56 ` Joerg Roedel [this message]
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=20190226105607.GI20740@8bytes.org \
--to=joro@8bytes.org \
--cc=ashok.raj@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=fenghua.yu@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=jisben@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=xmdong@google.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