From: Greg KH <gregkh@linuxfoundation.org>
To: Easwar Hariharan <eahariha@linux.microsoft.com>
Cc: stable@vger.kernel.org, easwar.hariharan@microsoft.com,
catalin.marinas@arm.com, will@kernel.org, corbet@lwn.net,
robin.murphy@arm.com, joro@8bytes.org,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Subject: Re: [PATCH 5.15 0/4] ARM64 errata for stable kernel 5.15 and above
Date: Fri, 21 Jul 2023 07:24:41 +0200 [thread overview]
Message-ID: <2023072113-charm-manual-de9e@gregkh> (raw)
In-Reply-To: <1689895414-17425-1-git-send-email-eahariha@linux.microsoft.com>
On Thu, Jul 20, 2023 at 04:23:30PM -0700, Easwar Hariharan wrote:
> From: Easwar Hariharan <easwar.hariharan@microsoft.com>
>
> This series works around a few ARM64 errata. Please pick these up for
> v6.1 and v6.4 as well.
The first 3 patches here are all in 6.1.y and 6.4.y, so how can they
also be added there?
thanks,
greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-07-21 5:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 23:23 [PATCH 5.15 0/4] ARM64 errata for stable kernel 5.15 and above Easwar Hariharan
2023-07-20 23:23 ` [PATCH 5.15 1/4] arm64: errata: Add detection for TRBE overwrite in FILL mode Easwar Hariharan
2023-07-21 5:40 ` Patch "arm64: errata: Add detection for TRBE overwrite in FILL mode" has been added to the 5.15-stable tree gregkh
2023-07-20 23:23 ` [PATCH 5.15 2/4] arm64: errata: Add workaround for TSB flush failures Easwar Hariharan
2023-07-21 5:27 ` Greg KH
2023-07-20 23:23 ` [PATCH 5.15 3/4] arm64: errata: Add detection for TRBE write to out-of-range Easwar Hariharan
2023-07-20 23:23 ` [PATCH 5.15 4/4] iommu/arm-smmu-v3: Document MMU-700 erratum 2812531 Easwar Hariharan
2023-07-21 5:24 ` 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=2023072113-charm-manual-de9e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=eahariha@linux.microsoft.com \
--cc=easwar.hariharan@microsoft.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=stable@vger.kernel.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).