All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: bp@alien8.de, mchehab@kernel.org,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: dmitry.baryshkov@linaro.org, james.morse@arm.com,
	rric@kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, linux-edac@vger.kernel.org
Subject: Re: [PATCH v8 0/2] Fix crash when using Qcom LLCC/EDAC drivers
Date: Fri, 26 May 2023 21:00:36 -0700	[thread overview]
Message-ID: <168516003598.405989.12832976179577504012.b4-ty@kernel.org> (raw)
In-Reply-To: <20230517114635.76358-1-manivannan.sadhasivam@linaro.org>

On Wed, 17 May 2023 17:16:33 +0530, Manivannan Sadhasivam wrote:
> This series fixes the crash seen on the Qualcomm SM8450 chipset with the
> LLCC/EDAC drivers. The problem was due to the Qcom EDAC driver using the
> fixed LLCC register offsets for detecting the LLCC errors.
> 
> This seems to have worked for SoCs till SM8450. But in SM8450, the LLCC
> register offsets were changed. So accessing the fixed offsets causes the
> crash on this platform.
> 
> [...]

Applied, thanks!

[1/2] EDAC/qcom: Remove superfluous return variable assignment in qcom_llcc_core_setup()
      commit: 3d49f7406b5d9822c1411c6658bac2ae55ba19a2
[2/2] EDAC/qcom: Get rid of hardcoded register offsets
      commit: cbd77119b6355872cd308a60e99f9ca678435d15

Best regards,
-- 
Bjorn Andersson <andersson@kernel.org>

      parent reply	other threads:[~2023-05-27  3:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17 11:46 [PATCH v8 0/2] Fix crash when using Qcom LLCC/EDAC drivers Manivannan Sadhasivam
2023-05-17 11:46 ` [PATCH v8 1/2] EDAC/qcom: Remove superfluous return variable assignment in qcom_llcc_core_setup() Manivannan Sadhasivam
2023-05-17 11:46 ` [PATCH v8 2/2] EDAC/qcom: Get rid of hardcoded register offsets Manivannan Sadhasivam
2023-05-27  4:00 ` Bjorn Andersson [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=168516003598.405989.12832976179577504012.b4-ty@kernel.org \
    --to=andersson@kernel.org \
    --cc=bp@alien8.de \
    --cc=dmitry.baryshkov@linaro.org \
    --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=rric@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 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.