From: Sasha Levin <sashal@kernel.org>
To: Lukas Wunner <lukas@wunner.de>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
Joel Mathew Thomas <proxy0@tutamail.com>
Subject: Re: Patch "PCI: pciehp: Ignore Link Down/Up caused by Secondary Bus Reset" has been added to the 6.15-stable tree
Date: Sat, 14 Jun 2025 12:11:48 -0400 [thread overview]
Message-ID: <aE2fRMmnmhJLBZ8w@lappy> (raw)
In-Reply-To: <aEuhJ_ldVUwI6u-V@wunner.de>
On Fri, Jun 13, 2025 at 05:55:19AM +0200, Lukas Wunner wrote:
>[cc += Joel Mathew Thomas]
>
>On Tue, Jun 10, 2025 at 08:16:05AM -0400, Sasha Levin wrote:
>> This is a note to let you know that I've just added the patch titled
>>
>> PCI: pciehp: Ignore Link Down/Up caused by Secondary Bus Reset
>>
>> to the 6.15-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-pciehp-ignore-link-down-up-caused-by-secondary-b.patch
>> and it can be found in the queue-6.15 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, thanks for selecting the above (which is 2af781a9edc4 upstream)
>as a 6.15 backport.
>
>A small feature request, could you amend the stable tooling to cc
>people tagged as Reported-by and Tested-by? I think they're the
>ones most interested in seeing something backported.
I'll see if git-send-email supports something like that...
--
Thanks,
Sasha
prev parent reply other threads:[~2025-06-14 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250610121606.1556304-1-sashal@kernel.org>
2025-06-13 3:55 ` Patch "PCI: pciehp: Ignore Link Down/Up caused by Secondary Bus Reset" has been added to the 6.15-stable tree Lukas Wunner
2025-06-14 16:11 ` Sasha Levin [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=aE2fRMmnmhJLBZ8w@lappy \
--to=sashal@kernel.org \
--cc=bhelgaas@google.com \
--cc=lukas@wunner.de \
--cc=proxy0@tutamail.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