From: Greg KH <gregkh@linuxfoundation.org>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: Patch "PCI: Preserve bridge window resource type flags" has been added to the 6.17-stable tree
Date: Mon, 13 Oct 2025 15:33:00 +0200 [thread overview]
Message-ID: <2025101348-conjuror-drapery-9fc1@gregkh> (raw)
In-Reply-To: <78ea57b6-5bc8-b357-c37c-bd327785e825@linux.intel.com>
On Mon, Oct 13, 2025 at 12:11:01PM +0300, Ilpo Järvinen wrote:
> On Sun, 12 Oct 2025, Sasha Levin wrote:
>
> > This is a note to let you know that I've just added the patch titled
> >
> > PCI: Preserve bridge window resource type flags
> >
> > to the 6.17-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > pci-preserve-bridge-window-resource-type-flags.patch
> > and it can be found in the queue-6.17 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
> Hi Sasha and other stable maintainers,
>
> While I agree the assessment that this is stable material, could we
> postpone queueing to stable a bit more? This change has relatively high
> regression potential and high impact for individual system that regresses,
> and is complicated change no matter what already given the diffstat alone.
>
> So try e.g. after 6.18 is released would seem more prudent for me as it
> would give more time to iron out problems in the rc-phase before any
> stable sees this change.
Ok, now dropped.
thanks,
greg k-h
prev parent reply other threads:[~2025-10-13 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251012141317.2894025-1-sashal@kernel.org>
2025-10-13 9:11 ` Patch "PCI: Preserve bridge window resource type flags" has been added to the 6.17-stable tree Ilpo Järvinen
2025-10-13 13:33 ` 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=2025101348-conjuror-drapery-9fc1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bhelgaas@google.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=stable-commits@vger.kernel.org \
--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