From: Greg KH <gregkh@linuxfoundation.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "Mendoza-jonas, Samuel" <samjonas@amazon.com>,
"Sironi, Filippo" <sironi@amazon.de>,
stable@vger.kernel.org, iommu <iommu@lists.linux-foundation.org>,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH] iommu/vt-d: gracefully handle DMAR units with no supported address widths
Date: Wed, 20 Jan 2021 13:06:48 +0100 [thread overview]
Message-ID: <YAgc2MX2c2N/rGDM@kroah.com> (raw)
In-Reply-To: <5414a3e3cdbd24ba707153584d13f06ed5dbba76.camel@infradead.org>
On Wed, Jan 20, 2021 at 09:42:43AM +0000, David Woodhouse wrote:
> On Thu, 2020-09-24 at 15:08 +0100, David Woodhouse wrote:
> > From: David Woodhouse <dwmw@amazon.co.uk>
> >
> > Instead of bailing out completely, such a unit can still be used for
> > interrupt remapping.
> >
> > Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
>
> Could we have this for stable too please, along with the trivial
> subsequent fixup. They are:
>
> c40aaaac1018 ("iommu/vt-d: Gracefully handle DMAR units with no supported address widths")
> 9def3b1a07c4 ("iommu/vt-d: Don't dereference iommu_device if IOMMU_API is not built")
>
> They apply fairly straightforwardly when backported; let me know if you
> want us to send patches.
What stable kernel(s) do you want this in? The above patches are
already in 5.10.
thanks,
greg k-h
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2021-01-20 12:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 14:08 [PATCH] iommu/vt-d: gracefully handle DMAR units with no supported address widths David Woodhouse
2020-09-25 1:52 ` Lu Baolu
2020-10-07 9:52 ` Joerg Roedel
2021-01-20 9:42 ` David Woodhouse
2021-01-20 12:06 ` Greg KH [this message]
2021-01-20 15:55 ` David Woodhouse
2021-01-20 17:04 ` Greg KH
2021-01-20 20:06 ` David Woodhouse
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=YAgc2MX2c2N/rGDM@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=samjonas@amazon.com \
--cc=sironi@amazon.de \
--cc=stable@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 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).