From: Joerg Roedel <joro@8bytes.org>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: iommu@lists.linux-foundation.org,
Adrian Huang <ahuang12@lenovo.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 1/1] iommu/vt-d: Fix double list_add when enabling VMD in scalable mode
Date: Mon, 28 Feb 2022 13:49:13 +0100 [thread overview]
Message-ID: <YhzEyfJ2Fa5Ikn+x@8bytes.org> (raw)
In-Reply-To: <20220221053348.262724-2-baolu.lu@linux.intel.com>
On Mon, Feb 21, 2022 at 01:33:48PM +0800, Lu Baolu wrote:
> Fixes: 474dd1c65064 ("iommu/vt-d: Fix clearing real DMA device's scalable-mode context entries")
> Cc: stable@vger.kernel.org # v5.14+
> Signed-off-by: Adrian Huang <ahuang12@lenovo.com>
> Link: https://lore.kernel.org/r/20220216091307.703-1-adrianhuang0701@gmail.com
> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
> ---
> drivers/iommu/intel/iommu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied for v5.17, 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: Adrian Huang <ahuang12@lenovo.com>,
iommu@lists.linux-foundation.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/1] iommu/vt-d: Fix double list_add when enabling VMD in scalable mode
Date: Mon, 28 Feb 2022 13:49:13 +0100 [thread overview]
Message-ID: <YhzEyfJ2Fa5Ikn+x@8bytes.org> (raw)
In-Reply-To: <20220221053348.262724-2-baolu.lu@linux.intel.com>
On Mon, Feb 21, 2022 at 01:33:48PM +0800, Lu Baolu wrote:
> Fixes: 474dd1c65064 ("iommu/vt-d: Fix clearing real DMA device's scalable-mode context entries")
> Cc: stable@vger.kernel.org # v5.14+
> Signed-off-by: Adrian Huang <ahuang12@lenovo.com>
> Link: https://lore.kernel.org/r/20220216091307.703-1-adrianhuang0701@gmail.com
> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
> ---
> drivers/iommu/intel/iommu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied for v5.17, thanks.
next prev parent reply other threads:[~2022-02-28 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 5:33 [PATCH 0/1] iommu/vt-d: Fixes for v5.17-rc6 Lu Baolu
2022-02-21 5:33 ` [PATCH 1/1] iommu/vt-d: Fix double list_add when enabling VMD in scalable mode Lu Baolu
2022-02-21 5:33 ` Lu Baolu
2022-02-28 12:49 ` Joerg Roedel [this message]
2022-02-28 12:49 ` 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=YhzEyfJ2Fa5Ikn+x@8bytes.org \
--to=joro@8bytes.org \
--cc=ahuang12@lenovo.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux-foundation.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 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.