From: Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"mika.westerberg@linux.intel.com"
<mika.westerberg@linux.intel.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
"logang@deltatee.com" <logang@deltatee.com>,
Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>
Subject: [PATCH 0/1] Fix bug resulting in double hpmemsize being assigned to MMIO window
Date: Thu, 7 Nov 2019 13:50:35 +0000 [thread overview]
Message-ID: <PS2P216MB075530CB1B7B099AAF9F42D580780@PS2P216MB0755.KORP216.PROD.OUTLOOK.COM> (raw)
I have split this patch off my main series, as I realised that it does
not need to be part of that series.
I have made some recent improvements to add assurance against it
breaking existing behaviour. Instead of returning the first resource of
the desired type regardless of it being assigned, now it goes through
all of the resources and returns only those of type that are not
assigned. Only then does it go through and return the first resource of
desired type that is assigned. If none are found then it returns NULL as
usual.
I have made extensive changes to the patch notes, also.
Logan Gunthorpe <logang@deltatee.com> has an alternative method of
fixing this same bug. Please also consider his patch and accept
whichever is best for Linux. All I care is that the bug be fixed.
Nicholas Johnson (1):
PCI: Fix bug resulting in double hpmemsize being assigned to MMIO
window
drivers/pci/setup-bus.c | 34 +++++++++++++++++++++++-----------
1 file changed, 23 insertions(+), 11 deletions(-)
--
2.23.0
next reply other threads:[~2019-11-07 13:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 13:50 Nicholas Johnson [this message]
2019-11-07 17:25 ` [PATCH 0/1] Fix bug resulting in double hpmemsize being assigned to MMIO window Logan Gunthorpe
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=PS2P216MB075530CB1B7B099AAF9F42D580780@PS2P216MB0755.KORP216.PROD.OUTLOOK.COM \
--to=nicholas.johnson-opensource@outlook.com.au \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=mika.westerberg@linux.intel.com \
/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).