From: Greg KH <gregkh@linuxfoundation.org>
To: Lucas Wei <lucaswei@google.com>
Cc: stable@vger.kernel.org, Daniel Mentz <danielmentz@google.com>,
Will Deacon <willdeacon@google.com>,
Robin Peng <robinpeng@google.com>,
Aaron Ding <aaronding@google.com>
Subject: Re: Request to cherry-pick into v5.15: arm64: errata: Add Cortex-A510 to the repeat tlbi list
Date: Tue, 30 Aug 2022 07:57:30 +0200 [thread overview]
Message-ID: <Yw2mylTWhMxTSSHY@kroah.com> (raw)
In-Reply-To: <CAPTxkvQXXeawY-LmmfVsM76MCUOQHRRQN=Sim7Fza0s0aAY6Rw@mail.gmail.com>
On Tue, Aug 30, 2022 at 10:31:35AM +0800, Lucas Wei wrote:
> Dear Linux stable kernel maintainers,
>
> I would like to apply the below patch into kernel v5.15-stable.
> - subject:arm64: errata: Add Cortex-A510 to the repeat tlbi list
> - Upstream Commit ID: 39fdb65f52e9a53d32a6ba719f96669fd300ae78
> - Targeted LTS release: v5.15
>
> This patch is an errata of #2441009. Since v5.15 is still in its LTS
> lifecycle, I think it fits the rule of "New device IDs and quirks are
> also accepted" and I want to request to apply this patch to kernel
> v5.15.
You also need it in 5.19.y, right? And you never want someone to
upgrade from an older kernel to a newer one and have a regression.
This commit does not cleanly cherry-pick, I need a working backport in
order to apply it. As I'm sure you already have a working and tested
backport of it (otherwise you wouldn't have asked for it), can you
please send it to us so that it can be applied?
Same for 5.19.y too.
thanks,
greg k-h
next prev parent reply other threads:[~2022-08-30 5:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPTxkvQJHAxYOSmXCro7Cf1uR4y202HTrYLVPCY0JNGc30Y0aA@mail.gmail.com>
2022-08-30 2:31 ` Request to cherry-pick into v5.15: arm64: errata: Add Cortex-A510 to the repeat tlbi list Lucas Wei
2022-08-30 5:57 ` Greg KH [this message]
2022-08-30 13:00 ` Lucas Wei
2022-08-30 13:14 ` 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=Yw2mylTWhMxTSSHY@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aaronding@google.com \
--cc=danielmentz@google.com \
--cc=lucaswei@google.com \
--cc=robinpeng@google.com \
--cc=stable@vger.kernel.org \
--cc=willdeacon@google.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