public inbox for linux-edac@vger.kernel.org
 help / color / mirror / Atom feed
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
Subject: Re: [PATCH v2 3/3] MAINTAINERS: Add myself as the maintainer for qcom_edac driver
Date: Wed, 26 Oct 2022 14:38:18 +0200	[thread overview]
Message-ID: <Y1kqOqhQeGkfoQnp@zn.tnic> (raw)
In-Reply-To: <20220812060602.7672-4-manivannan.sadhasivam@linaro.org>

On Fri, Aug 12, 2022 at 11:36:02AM +0530, Manivannan Sadhasivam wrote:
> The current maintainers have left Qualcomm and their email addresses were
> bouncing. Since I couldn't get hold of them now, I'm volunteering myself
> to maintain this driver.
> 
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> ---
>  MAINTAINERS | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)

Applied, thanks.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

      parent reply	other threads:[~2022-10-26 12:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-12  6:05 [PATCH v2 0/3] Fix crash when using Qcom LLCC/EDAC drivers Manivannan Sadhasivam
2022-08-12  6:06 ` [PATCH v2 1/3] soc: qcom: llcc: Pass SoC specific EDAC register offsets to EDAC driver Manivannan Sadhasivam
2022-08-22 11:59   ` Sai Prakash Ranjan
2022-08-23 15:31     ` Manivannan Sadhasivam
2022-08-24  5:13       ` Sai Prakash Ranjan
2022-08-24 12:57         ` Manivannan Sadhasivam
2022-08-24 13:07           ` Sai Prakash Ranjan
2022-08-12  6:06 ` [PATCH v2 2/3] EDAC/qcom: Get rid of hardcoded register offsets Manivannan Sadhasivam
2022-08-12  6:06 ` [PATCH v2 3/3] MAINTAINERS: Add myself as the maintainer for qcom_edac driver Manivannan Sadhasivam
2022-08-22 11:43   ` Sai Prakash Ranjan
2022-10-26 12:38   ` 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=Y1kqOqhQeGkfoQnp@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_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