From: Breno Leitao <leitao@debian.org>
To: gregkh@linuxfoundation.org
Cc: andi.shyti@kernel.org, andy@kernel.org, digetx@gmail.com,
rmikey@meta.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] i2c: tegra: Do not mark ACPI devices as irq safe" failed to apply to 6.1-stable tree
Date: Tue, 20 Aug 2024 01:14:29 -0700 [thread overview]
Message-ID: <ZsRQZZiSo2sj5EaI@gmail.com> (raw)
In-Reply-To: <2024081950-amaze-wriggle-3057@gregkh>
Hello Greg,
On Mon, Aug 19, 2024 at 11:31:50AM +0200, gregkh@linuxfoundation.org wrote:
>
> The patch below does not apply to the 6.1-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.
I am working to backport this fix to 6.1 and I should have a patch ready
soon.
Thanks
next prev parent reply other threads:[~2024-08-20 8:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 9:31 FAILED: patch "[PATCH] i2c: tegra: Do not mark ACPI devices as irq safe" failed to apply to 6.1-stable tree gregkh
2024-08-20 8:14 ` Breno Leitao [this message]
2024-08-23 8:38 ` [PATCH 6.1.y] i2c: tegra: Do not mark ACPI devices as irq safe Breno Leitao
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=ZsRQZZiSo2sj5EaI@gmail.com \
--to=leitao@debian.org \
--cc=andi.shyti@kernel.org \
--cc=andy@kernel.org \
--cc=digetx@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=rmikey@meta.com \
--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