From: Sean Anderson <sean.anderson@linux.dev>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, bartosz.golaszewski@linaro.org
Subject: Re: [PATCH 6.1.y v2] gpio: xilinx: Convert gpio_lock to raw spinlock
Date: Thu, 30 Jan 2025 11:01:23 -0500 [thread overview]
Message-ID: <eaf0535a-3ebf-457f-bc07-2e182a0a6625@linux.dev> (raw)
In-Reply-To: <2025012905-oasis-babied-261b@gregkh>
Hi Greg,
On 1/29/25 04:14, Greg KH wrote:
> On Tue, Jan 21, 2025 at 02:32:06PM -0500, Sean Anderson wrote:
>> [ Upstream commit 9860370c2172704b6b4f0075a0c2a29fd84af96a ]
>
> For obvious reasons we can't take patches just for older trees because
> if you update to a newer stable/lts version, you will have a regression.
> Please submit backports for all relevant versions and then we will be
> glad to queue them up.
The upstream commit is in 6.13 [1]. Additionally, you have posted patches
for 6.12 [2] and 6.6 [2]. This just fixes the patch for 6.1 [4].
--Sean
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9860370c2172704b6b4f0075a0c2a29fd84af96a
[2] https://lore.kernel.org/stable/20250121174536.648642765@linuxfoundation.org/
[3] https://lore.kernel.org/stable/20250121174525.472060737@linuxfoundation.org/
[4] https://lore.kernel.org/stable/2025012027-shaft-catalyst-2d69@gregkh/
prev parent reply other threads:[~2025-01-30 16:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 13:44 FAILED: patch "[PATCH] gpio: xilinx: Convert gpio_lock to raw spinlock" failed to apply to 6.1-stable tree gregkh
2025-01-21 18:41 ` [PATCH 6.1.y] gpio: xilinx: Convert gpio_lock to raw spinlock Sean Anderson
2025-01-21 19:27 ` Sean Anderson
2025-01-21 19:32 ` [PATCH 6.1.y v2] " Sean Anderson
2025-01-21 20:08 ` Sasha Levin
2025-01-29 9:14 ` Greg KH
2025-01-30 16:01 ` Sean Anderson [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=eaf0535a-3ebf-457f-bc07-2e182a0a6625@linux.dev \
--to=sean.anderson@linux.dev \
--cc=bartosz.golaszewski@linaro.org \
--cc=gregkh@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.