From: Borislav Petkov <bp@alien8.de>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: bjorn.andersson@linaro.org, ckadabi@quicinc.com,
vnkgutta@quicinc.com, 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,
Channagoud Kadabi <ckadabi@codeaurora.org>,
Venkata Narendra Kumar Gutta <vnkgutta@codeaurora.org>
Subject: Re: [PATCH 0/2] Fix crash when using Qcom LLCC/EDAC drivers
Date: Thu, 11 Aug 2022 13:33:06 +0200 [thread overview]
Message-ID: <YvTo8tE3DaHifrSp@zn.tnic> (raw)
In-Reply-To: <20220811112032.GB29799@workstation>
On Thu, Aug 11, 2022 at 04:50:32PM +0530, Manivannan Sadhasivam wrote:
> I know get_maintainer.pl :) But the problem is, Qualcomm recently
> switched their email domain from codeaurora.org to quicinc.com.
Great:
$ git grep codeaurora.org MAINTAINERS | wc -l
5
;-\
> So even if I use the maintainers codeaurora domain now, they will
> bounce.
Hmm, so the mails I sent with codeaurora on Cc didn't bounce back - I
got only the quicinc bounces. That doesn't mean that codeaurora actually
gets delivered...
> For that reason, I used their quicinc domain addresses. But since they
> are bouncing, it looks like the maintainers left Qualcomm :/
Hmm, is there some way to get in touch with those folks?
Or whoever is taking over those drivers?
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-08-11 11:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 10:09 [PATCH 0/2] Fix crash when using Qcom LLCC/EDAC drivers Manivannan Sadhasivam
2022-08-11 10:09 ` [PATCH 1/2] soc: qcom: llcc: Pass SoC specific EDAC register offsets to EDAC driver Manivannan Sadhasivam
2022-08-11 10:09 ` [PATCH 2/2] EDAC/qcom: Get rid of hardcoded register offsets Manivannan Sadhasivam
2022-08-11 10:48 ` [PATCH 0/2] Fix crash when using Qcom LLCC/EDAC drivers Borislav Petkov
2022-08-11 10:53 ` Borislav Petkov
2022-08-11 11:20 ` Manivannan Sadhasivam
2022-08-11 11:33 ` Borislav Petkov [this message]
2022-08-11 11:53 ` Manivannan Sadhasivam
2022-08-11 11:57 ` Manivannan Sadhasivam
2022-08-11 16:08 ` Trilok Soni
2022-08-12 5:35 ` Manivannan Sadhasivam
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=YvTo8tE3DaHifrSp@zn.tnic \
--to=bp@alien8.de \
--cc=bjorn.andersson@linaro.org \
--cc=ckadabi@codeaurora.org \
--cc=ckadabi@quicinc.com \
--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 \
--cc=vnkgutta@codeaurora.org \
--cc=vnkgutta@quicinc.com \
/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