public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Filippo Sironi <sironi@amazon.de>
Cc: stable@vger.kernel.org, samjonas@amazon.com, dwmw@amazon.co.uk,
	Joerg Roedel <jroedel@suse.de>
Subject: Re: [PATCH 1/2 for Linux 5.4] iommu/vt-d: Gracefully handle DMAR units with no supported address widths
Date: Tue, 2 Feb 2021 14:04:32 +0100	[thread overview]
Message-ID: <YBlN4JmzxKrt6O9G@kroah.com> (raw)
In-Reply-To: <20210202000009.31392-1-sironi@amazon.de>

On Tue, Feb 02, 2021 at 01:00:08AM +0100, Filippo Sironi wrote:
> From: David Woodhouse <dwmw@amazon.co.uk>
> 
> commit c40aaaac1018ff1382f2d35df5129a6bcea3df6b upstream.
> 
> Instead of bailing out completely, such a unit can still be used for
> interrupt remapping.
> 
> Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
> Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com>
> Link: https://lore.kernel.org/linux-iommu/549928db2de6532117f36c9c810373c14cf76f51.camel@infradead.org/
> Signed-off-by: Joerg Roedel <jroedel@suse.de>
> [ context change due to moving drivers/iommu/dmar.c to
>   drivers/iommu/intel/dmar.c ]
> Signed-off-by: Filippo Sironi <sironi@amazon.de>
> ---
>  drivers/iommu/dmar.c | 44 ++++++++++++++++++++++++++++++--------------
>  1 file changed, 30 insertions(+), 14 deletions(-)

All of these now queued up, thanks!

greg k-h

      parent reply	other threads:[~2021-02-02 13:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02  0:00 [PATCH 1/2 for Linux 5.4] iommu/vt-d: Gracefully handle DMAR units with no supported address widths Filippo Sironi
2021-02-02  0:00 ` [PATCH 2/2 for Linux 5.4] iommu/vt-d: Don't dereference iommu_device if IOMMU_API is not built Filippo Sironi
2021-02-02 13:04 ` Greg KH [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=YBlN4JmzxKrt6O9G@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dwmw@amazon.co.uk \
    --cc=jroedel@suse.de \
    --cc=samjonas@amazon.com \
    --cc=sironi@amazon.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox