From: Thomas Backlund <tmb@iki.fi>
To: Hans de Goede <hdegoede@redhat.com>, Bjorn Helgaas <helgaas@kernel.org>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
"Mika Westerberg" <mika.westerberg@linux.intel.com>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Myron Stowe" <myron.stowe@redhat.com>,
"Juha-Pekka Heikkila" <juhapekka.heikkila@gmail.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Borislav Petkov" <bp@alien8.de>,
"H . Peter Anvin" <hpa@zytor.com>,
linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
x86@kernel.org, linux-kernel@vger.kernel.org,
"Benoit Grégoire" <benoitg@coeus.ca>,
"Hui Wang" <hui.wang@canonical.com>,
stable@vger.kernel.org,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH v5 1/2] x86/PCI: Ignore E820 reservations for bridge windows on newer systems
Date: Wed, 10 Nov 2021 23:51:31 +0200 [thread overview]
Message-ID: <958106af-e5ae-af6a-478d-c1eaef8e1498@iki.fi> (raw)
In-Reply-To: <1a001812-1f18-1999-44b7-30fe3a19f460@redhat.com>
Den 2021-11-10 kl. 15:05, skrev Hans de Goede:
>
> So I've discussed this with the Fedora kernel maintainers and they have
> agreed to add the patch to the Fedora 5.15 kernels, which we will ask
> our users to start testing soon (we first run some voluntary testing
> before eventually moving all users over).
>
> This will provide us with valuable feedback wrt this patch causing
> regressions as you are worried about, or not.
>
> Assuming no regressions show up I hope that this will give you
> some assurance that there the patch causes no regressions and that
> you will then be willing to pick this up later during the 5.16
> cycle so that Fedora only deviates from upstream for 1 cycle.
>
FWIW... As an extra data point...
I've backported this one on top of 5.14.14 in Mageia Cauldron and Mageia
8 backports where it has been in active use for ~3 weeks now, and so far
no reports of systems breaking ...
--
Thomas
next prev parent reply other threads:[~2021-11-10 21:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bfbac749-7434-1497-039b-3b8bc4dc5499@redhat.com>
2021-10-20 21:14 ` Bjorn Helgaas
2021-10-21 17:15 ` Hans de Goede
2021-10-22 1:20 ` Bjorn Helgaas
2021-10-22 9:53 ` Hans de Goede
2021-10-29 8:10 ` Hans de Goede
2021-11-06 10:15 ` Hans de Goede
2021-11-09 22:07 ` Bjorn Helgaas
2021-11-10 8:45 ` Hans de Goede
2021-11-10 13:05 ` Hans de Goede
2021-11-10 21:51 ` Thomas Backlund [this message]
2021-12-07 16:52 ` Hans de Goede
2021-12-15 16:01 ` Bjorn Helgaas
2021-12-15 16:33 ` Hans de Goede
2021-10-14 18:39 [PATCH v5 0/2] " Hans de Goede
2021-10-14 18:39 ` [PATCH v5 1/2] " Hans de Goede
2021-10-15 20:03 ` Bjorn Helgaas
2021-10-15 20:15 ` Hans de Goede
2021-10-19 21:52 ` Bjorn Helgaas
2021-10-19 21:55 ` Bjorn Helgaas
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=958106af-e5ae-af6a-478d-c1eaef8e1498@iki.fi \
--to=tmb@iki.fi \
--cc=benoitg@coeus.ca \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=hdegoede@redhat.com \
--cc=helgaas@kernel.org \
--cc=hpa@zytor.com \
--cc=hui.wang@canonical.com \
--cc=juhapekka.heikkila@gmail.com \
--cc=kw@linux.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=mingo@redhat.com \
--cc=myron.stowe@redhat.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®