From: Greg KH <gregkh@linuxfoundation.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
bp@alien8.de, mchehab@kernel.org, james.morse@arm.com,
rric@kernel.org, linux-arm-msm@vger.kernel.org,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
quic_saipraka@quicinc.com, stable@vger.kernel.org
Subject: Re: [PATCH v6 2/2] EDAC/qcom: Get rid of hardcoded register offsets
Date: Mon, 10 Apr 2023 20:32:20 +0200 [thread overview]
Message-ID: <2023041047-oboe-playmaker-ca1b@gregkh> (raw)
In-Reply-To: <20230410155111.GB4630@thinkpad>
On Mon, Apr 10, 2023 at 09:21:11PM +0530, Manivannan Sadhasivam wrote:
> On Wed, Mar 15, 2023 at 03:22:42PM -0700, Bjorn Andersson wrote:
> > On Tue, Mar 14, 2023 at 12:10:32PM +0530, Manivannan Sadhasivam wrote:
> > > The LLCC EDAC register offsets varies between each SoC. Hardcoding the
> > > register offsets won't work and will often result in crash due to
> > > accessing the wrong locations.
> > >
> > > Hence, get the register offsets from the LLCC driver matching the
> > > individual SoCs.
> > >
> > > Cc: <stable@vger.kernel.org> # 6.0: 5365cea199c7 ("soc: qcom: llcc: Rename reg_offset structs to reflect LLCC version")
> > > Cc: <stable@vger.kernel.org> # 6.0: c13d7d261e36 ("soc: qcom: llcc: Pass LLCC version based register offsets to EDAC driver")
> > > Cc: <stable@vger.kernel.org> # 6.0
> >
> > Why is there three Cc: stable here, is this a new format for Fixes:?
> >
>
> This is to specify the dependencies to the stable maintainers during backport.
And that format has been documented for well over a decade in:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
This is nothing new :)
thanks,
greg k-h
next prev parent reply other threads:[~2023-04-10 18:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 6:40 [PATCH v6 0/2] Fix crash when using Qcom LLCC/EDAC drivers Manivannan Sadhasivam
2023-03-14 6:40 ` [PATCH v6 1/2] EDAC/qcom: Remove extra error no assignment in qcom_llcc_core_setup() Manivannan Sadhasivam
2023-03-14 6:40 ` [PATCH v6 2/2] EDAC/qcom: Get rid of hardcoded register offsets Manivannan Sadhasivam
2023-03-15 22:22 ` Bjorn Andersson
2023-04-10 15:51 ` Manivannan Sadhasivam
2023-04-10 18:32 ` Greg KH [this message]
2023-05-11 16:12 ` Dmitry Baryshkov
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=2023041047-oboe-playmaker-ca1b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andersson@kernel.org \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mchehab@kernel.org \
--cc=quic_saipraka@quicinc.com \
--cc=rric@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).