From: Bjorn Helgaas <helgaas@kernel.org>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>,
linux-pci@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Steve Oswald <stevepeter.oswald@gmail.com>
Subject: Re: [PATCH v2 1/1] PCI: Prevent shrinking bridge window from its required size
Date: Fri, 20 Feb 2026 09:01:20 -0600 [thread overview]
Message-ID: <20260220150120.GA3525869@bhelgaas> (raw)
In-Reply-To: <0a425bb6-f08b-0aee-c494-843e42150a2f@linux.intel.com>
On Fri, Feb 20, 2026 at 01:32:43PM +0200, Ilpo Järvinen wrote:
> On Thu, 19 Feb 2026, Bjorn Helgaas wrote:
> ...
> > These both date back to v5.10 (Dec 2020), but Steve's report below is
> > only from Aug 2025, so I'm sort of assuming this is v7.1 material?
>
> It's an old problem yes and impacts limited set of configurations
> (a device with big BARs attached to TB).
>
> v7.1 is okay for me, this could cause some not immediately obvious problem
> in some other case so it gives more time for us to hear about them
> (hopefully).
>
> > If we want it for v7.0, I'm going to need a CliffsNotes summary of the
> > commit log to justify it :)
>
> Even if it's not going to be needed in this cases, what's "CliffsNotes
> summary" ??
Slang for a short summary :) I.e., a sentence or two to motivate a
pull request. Big BARs attached via Thunderbolt sounds like an
important piece; e.g., maybe this helps fix Thunderbolt docks with
GPUs in them?
next prev parent reply other threads:[~2026-02-20 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 15:39 [PATCH v2 1/1] PCI: Prevent shrinking bridge window from its required size Ilpo Järvinen
2026-02-19 23:16 ` Bjorn Helgaas
2026-02-20 11:32 ` Ilpo Järvinen
2026-02-20 15:01 ` Bjorn Helgaas [this message]
2026-02-20 15:47 ` Ilpo Järvinen
2026-03-26 20:04 ` 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=20260220150120.GA3525869@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=nicholas.johnson-opensource@outlook.com.au \
--cc=stevepeter.oswald@gmail.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