From: Greg KH <gregkh@linuxfoundation.org>
To: Terry Tritton <terry.tritton@linaro.org>
Cc: stable <stable@vger.kernel.org>, Vidya Sagar <vidyas@nvidia.com>,
Sasha Levin <sashal@kernel.org>,
Daniel Verkamp <dverkamp@chromium.org>
Subject: Re: [REGRESSION] Cuttlefish boot issue on lts branches
Date: Fri, 17 Jan 2025 15:09:58 +0100 [thread overview]
Message-ID: <2025011710-chug-hefty-2fd6@gregkh> (raw)
In-Reply-To: <CABeuJB3xEQfgx1TiKyxREQjTJ6jh=xt=N7bTQoKgjAN1Xoa5WA@mail.gmail.com>
On Fri, Jan 17, 2025 at 01:34:14PM +0000, Terry Tritton wrote:
> Thanks Greg,
> whats the best way to do that?
> Do you need a patch for each lts branch affected or just one based on stable?
One for each branch please, as the git ids for the commit is different
on each one, right?
Look at commit acddb8762014 ("Revert "rcu-tasks: Fix access non-existent
percpu rtpcp variable in rcu_tasks_need_gpcb()"") for an idea of how to
write the header.
thanks,
greg k-h
next prev parent reply other threads:[~2025-01-17 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 11:01 [REGRESSION] Cuttlefish boot issue on lts branches Terry Tritton
2025-01-17 11:23 ` Greg KH
2025-01-17 13:34 ` Terry Tritton
2025-01-17 14:09 ` Greg KH [this message]
2025-01-17 15:18 ` Terry Tritton
2025-01-17 15:38 ` Greg KH
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=2025011710-chug-hefty-2fd6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dverkamp@chromium.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=terry.tritton@linaro.org \
--cc=vidyas@nvidia.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