From: Joerg Roedel <joro@8bytes.org>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
ashok.raj@intel.com, jacob.jun.pan@intel.com,
kevin.tian@intel.com, yi.l.liu@intel.com,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
Jacob Pan <jacob.jun.pan@linux.intel.com>
Subject: Re: [PATCH 1/1] iommu/vt-d: Don't request page request irq under dmar_global_lock
Date: Fri, 26 Apr 2019 16:45:21 +0200 [thread overview]
Message-ID: <20190426144521.GI24576@8bytes.org> (raw)
In-Reply-To: <20190419064329.17946-1-baolu.lu@linux.intel.com>
On Fri, Apr 19, 2019 at 02:43:29PM +0800, Lu Baolu wrote:
> drivers/iommu/intel-iommu.c | 6 ++++++
> 1 file changed, 6 insertions(+)
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: kevin.tian@intel.com, ashok.raj@intel.com,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
jacob.jun.pan@intel.com, David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 1/1] iommu/vt-d: Don't request page request irq under dmar_global_lock
Date: Fri, 26 Apr 2019 16:45:21 +0200 [thread overview]
Message-ID: <20190426144521.GI24576@8bytes.org> (raw)
Message-ID: <20190426144521.B0CrAnQ3FbS-72By552yxX7N0K0OZzB1aOkGy47b0lQ@z> (raw)
In-Reply-To: <20190419064329.17946-1-baolu.lu@linux.intel.com>
On Fri, Apr 19, 2019 at 02:43:29PM +0800, Lu Baolu wrote:
> drivers/iommu/intel-iommu.c | 6 ++++++
> 1 file changed, 6 insertions(+)
Applied, thanks.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2019-04-26 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 6:43 [PATCH 1/1] iommu/vt-d: Don't request page request irq under dmar_global_lock Lu Baolu
2019-04-19 6:43 ` Lu Baolu
2019-04-19 6:43 ` Lu Baolu
2019-04-26 14:45 ` Joerg Roedel [this message]
2019-04-26 14:45 ` Joerg Roedel
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=20190426144521.GI24576@8bytes.org \
--to=joro@8bytes.org \
--cc=ashok.raj@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@intel.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yi.l.liu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.