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 16:38:03 +0100 [thread overview]
Message-ID: <2025011749-rust-bartender-9ecb@gregkh> (raw)
In-Reply-To: <CABeuJB0jMbysm06guUvCA_O9Dbqmd6n0X93deiVtqgQwWW9TQA@mail.gmail.com>
On Fri, Jan 17, 2025 at 03:18:01PM +0000, Terry Tritton wrote:
> > One for each branch please, as the git ids for the commit is different
> > on each one, right?
>
> Thanks that's what I assumed but wasn't sure if there was some script
> that did some magic.
>
> Sent those to stable now, let me know if there are any issues.
Looks good, I'll get to them next week...
greg k-h
prev parent reply other threads:[~2025-01-17 15:38 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
2025-01-17 15:18 ` Terry Tritton
2025-01-17 15:38 ` 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=2025011749-rust-bartender-9ecb@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 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.