From: Borislav Petkov <bp@alien8.de>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: bjorn.andersson@linaro.org, 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_tsoni@quicinc.com,
quic_saipraka@quicinc.com
Subject: Re: [PATCH v3 0/5] Fix crash when using Qcom LLCC/EDAC drivers
Date: Mon, 3 Oct 2022 11:32:48 +0200 [thread overview]
Message-ID: <YzqsQD3EFGzCEQJf@zn.tnic> (raw)
In-Reply-To: <20221003070415.GC5398@thinkpad>
On Mon, Oct 03, 2022 at 12:34:15PM +0530, Manivannan Sadhasivam wrote:
> Since the LLCC patches are already merged, can we get the EDAC patches to be
> merged for v6.1?
It is too late for 6.1. I'll take a look at them after the merge window closes.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2022-10-03 9:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 4:38 [PATCH v3 0/5] Fix crash when using Qcom LLCC/EDAC drivers Manivannan Sadhasivam
2022-08-25 4:38 ` [PATCH v3 1/5] soc: qcom: llcc: Rename reg_offset structs to reflect LLCC version Manivannan Sadhasivam
2022-08-25 4:48 ` Sai Prakash Ranjan
2022-08-25 4:38 ` [PATCH v3 2/5] soc: qcom: llcc: Pass LLCC version based register offsets to EDAC driver Manivannan Sadhasivam
2022-08-25 4:50 ` Sai Prakash Ranjan
2022-08-25 4:38 ` [PATCH v3 3/5] EDAC/qcom: Get rid of hardcoded register offsets Manivannan Sadhasivam
2022-08-25 4:57 ` Sai Prakash Ranjan
2022-08-30 2:50 ` Bjorn Andersson
2022-10-26 16:00 ` Borislav Petkov
2022-08-25 4:38 ` [PATCH v3 4/5] EDAC/qcom: Remove extra error no assignment in qcom_llcc_core_setup() Manivannan Sadhasivam
2022-08-25 4:45 ` Sai Prakash Ranjan
2022-08-25 4:38 ` [PATCH v3 5/5] MAINTAINERS: Add myself as the maintainer for qcom_edac driver Manivannan Sadhasivam
2022-08-30 2:50 ` (subset) [PATCH v3 0/5] Fix crash when using Qcom LLCC/EDAC drivers Bjorn Andersson
2022-10-03 7:04 ` Manivannan Sadhasivam
2022-10-03 9:32 ` Borislav Petkov [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=YzqsQD3EFGzCEQJf@zn.tnic \
--to=bp@alien8.de \
--cc=bjorn.andersson@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=quic_saipraka@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox