iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Greg KH <gregkh@linuxfoundation.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 20:06:51 +0000	[thread overview]
Message-ID: <0bb6f0199ff0b1aad7dc3b641dc41cf1492c3183.camel@infradead.org> (raw)
In-Reply-To: <YAhikV3sOsyRVDyh@kroah.com>


[-- Attachment #1.1: Type: text/plain, Size: 619 bytes --]

On Wed, 2021-01-20 at 18:04 +0100, Greg KH wrote:
> I tried applying these to 5.4, 4.19, and 4.14, and they all fail to
> build:
> 
> drivers/iommu/dmar.c: In function ‘free_iommu’:
> drivers/iommu/dmar.c:1140:35: error: ‘struct intel_iommu’ has no member named ‘drhd’
>  1140 |  if (intel_iommu_enabled && !iommu->drhd->ignored) {
>       |                                   ^~
> 
> So if you could provide a working set of patches backported, I will be
> glad to queue them up.

Thanks.

I'm just heckling at Sam's backport of those, and we'll post tested
patches as soon as we're done.


[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5174 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

      reply	other threads:[~2021-01-20 20:09 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
2021-01-20 15:55     ` David Woodhouse
2021-01-20 17:04       ` Greg KH
2021-01-20 20:06         ` David Woodhouse [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=0bb6f0199ff0b1aad7dc3b641dc41cf1492c3183.camel@infradead.org \
    --to=dwmw2@infradead.org \
    --cc=gregkh@linuxfoundation.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).