From: Greg KH <gregkh@linuxfoundation.org>
To: Jason Andryuk <jandryuk@gmail.com>
Cc: stable@vger.kernel.org, Juergen Gross <jgross@suse.com>,
Borislav Petkov <bp@alien8.de>,
Christian Kujau <lists@nerdbynature.de>
Subject: Re: Request: x86/mtrr: Revert 90b926e68f50 ("x86/pat: Fix pat_x_mtrr_type() for MTRR disabled case")
Date: Mon, 5 Jun 2023 21:48:23 +0200 [thread overview]
Message-ID: <2023060513-self-ditch-57f5@gregkh> (raw)
In-Reply-To: <CAKf6xptzGSq5xUhbFDVB-vR0WfhDWnqXRY3UYYG4DvUakNR1AQ@mail.gmail.com>
On Mon, Jun 05, 2023 at 09:56:24AM -0400, Jason Andryuk wrote:
> x86/mtrr: Revert 90b926e68f50 ("x86/pat: Fix pat_x_mtrr_type() for
> MTRR disabled case")
>
> commit f9f57da2c2d119dbf109e3f6e1ceab7659294046 upstream
>
> The requested patch fixes ioremap for certain devices when running as
> a Xen Dom0. Without the patch, one example is TPM device probing
> failing with:
> tpm_tis IFX:00: ioremap failed for resource
>
> The requested patch did not include a Fixes tag, but it was intended
> as a fix to upstream 90b926e68f500844dff16b5bcea178dc55cf580a, which
> was subsequently backported to 6.1 as
> c1c59538337ab6d45700cb4a1c9725e67f59bc6e. The requested patch being a
> fix can be seen in the thread here:
> https://lore.kernel.org/lkml/167636735608.4906.4788207020350311572.tip-bot2@tip-bot2/
>
> I think it's only applicable to 6.1
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-06-05 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 13:56 Request: x86/mtrr: Revert 90b926e68f50 ("x86/pat: Fix pat_x_mtrr_type() for MTRR disabled case") Jason Andryuk
2023-06-05 19:48 ` 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=2023060513-self-ditch-57f5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bp@alien8.de \
--cc=jandryuk@gmail.com \
--cc=jgross@suse.com \
--cc=lists@nerdbynature.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 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.