From: Joerg Roedel <joro@8bytes.org>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: Dave Jiang <dave.jiang@intel.com>,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH v2 1/1] iommu/vt-d: Don't set then clear private data in prq_event_thread()
Date: Wed, 7 Apr 2021 10:10:18 +0200 [thread overview]
Message-ID: <YG1o6tlQ9phFHCe4@8bytes.org> (raw)
In-Reply-To: <20210320024156.640798-1-baolu.lu@linux.intel.com>
On Sat, Mar 20, 2021 at 10:41:56AM +0800, Lu Baolu wrote:
> drivers/iommu/intel/svm.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Applied, thanks.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: Will Deacon <will@kernel.org>, Dave Jiang <dave.jiang@intel.com>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
Liu Yi L <yi.l.liu@intel.com>
Subject: Re: [PATCH v2 1/1] iommu/vt-d: Don't set then clear private data in prq_event_thread()
Date: Wed, 7 Apr 2021 10:10:18 +0200 [thread overview]
Message-ID: <YG1o6tlQ9phFHCe4@8bytes.org> (raw)
In-Reply-To: <20210320024156.640798-1-baolu.lu@linux.intel.com>
On Sat, Mar 20, 2021 at 10:41:56AM +0800, Lu Baolu wrote:
> drivers/iommu/intel/svm.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Applied, thanks.
next prev parent reply other threads:[~2021-04-07 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 2:41 [PATCH v2 1/1] iommu/vt-d: Don't set then clear private data in prq_event_thread() Lu Baolu
2021-03-20 2:41 ` Lu Baolu
2021-04-07 8:10 ` Joerg Roedel [this message]
2021-04-07 8:10 ` 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=YG1o6tlQ9phFHCe4@8bytes.org \
--to=joro@8bytes.org \
--cc=baolu.lu@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will@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 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.