From: Borislav Petkov <bp@alien8.de>
To: Ryan Chen <ryan_chen@aspeedtech.com>
Cc: Stefan Schaeckeler <sschaeck@cisco.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
Tony Luck <tony.luck@intel.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
Borislav Petkov <bp@suse.de>,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v3 0/9] Add Aspeed AST2700 SDRAM EDAC support
Date: Mon, 21 Sep 2026 20:19:05 -0700 [thread overview]
Message-ID: <20260922031905.GEarHzqf56ypqALDHi@fat_crate.local> (raw)
In-Reply-To: <TY2PPF5CB9A1BE6D0247845980A7BD60E60F2832@TY2PPF5CB9A1BE6.apcprd06.prod.outlook.com>
Hi Ryan,
On Tue, Sep 22, 2026 at 02:53:27AM +0000, Ryan Chen wrote:
> Stefan has resigned from the EDAC entry:
>
> https://lkml.org/lkml/2026/9/20/1295
Please do not use rando pages from search engines for pointing to patches, we
have lore.kernel.org for that.
Also, please do not top-post on public MLs but put your text under the text
you're replying to.
We have the whole development process explained here, please take some time to
read the most important points:
https://www.kernel.org/doc/html/latest/process/development-process.html
> That leaves his patch and 9/9 of this series touching the same lines,
> and the entry ending up with a reviewer and no maintainer.
>
> You suggested a reviewer entry first, and I understood the reasoning.
> But with Stefan gone the choice is now between orphaning the driver and
> someone taking it, so I'd rather ask again: I'm happy to take the M:
> line. I work on these SoCs at ASPEED and have the hardware and the
> documentation for all four variants.
That's much appreciated but you don't have to worry - the driver won't be
orphaned and you'll be the reviewer and tester of patches for it. And I'll
simply add Stefan's patch at the end and amend the hunk marking the driver as
orphan and instead add your hunk which is making you a reviewer.
> If you'd still rather not, that's fine - tell me and I'll respin 9/9 so
> the entry reflects reality instead.
Let's see how we work together this way first.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2026-09-22 3:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 5:30 [PATCH v3 0/9] Add Aspeed AST2700 SDRAM EDAC support Ryan Chen
2026-09-16 5:30 ` [PATCH v3 1/9] dt-bindings: edac: aspeed: Add AST2700 SDRAM EDAC Ryan Chen
2026-09-16 5:30 ` [PATCH v3 2/9] EDAC/aspeed: Set the DIMM grain Ryan Chen
2026-09-25 5:45 ` Borislav Petkov
2026-09-29 6:59 ` Ryan Chen
2026-09-16 5:30 ` [PATCH v3 3/9] EDAC/aspeed: Free the interrupt before the mem_ctl_info on remove Ryan Chen
2026-09-16 5:30 ` [PATCH v3 4/9] EDAC/aspeed: Clean up whitespace and include ordering Ryan Chen
2026-09-16 5:30 ` [PATCH v3 5/9] EDAC/aspeed: Free the mem_ctl_info unconditionally on remove Ryan Chen
2026-09-16 5:30 ` [PATCH v3 6/9] EDAC/aspeed: Replace regmap with direct register access Ryan Chen
2026-09-16 5:40 ` sashiko-bot
2026-09-16 5:46 ` Ryan Chen
2026-09-16 5:30 ` [PATCH v3 7/9] EDAC/aspeed: Abstract SoC differences behind chip data Ryan Chen
2026-09-16 5:30 ` [PATCH v3 8/9] EDAC/aspeed: Add AST2700 support Ryan Chen
2026-09-16 5:30 ` [PATCH v3 9/9] MAINTAINERS: Add a reviewer for the Aspeed EDAC driver Ryan Chen
2026-09-22 2:53 ` [PATCH v3 0/9] Add Aspeed AST2700 SDRAM EDAC support Ryan Chen
2026-09-22 3:19 ` Borislav Petkov [this message]
2026-09-22 5:25 ` Ryan Chen
2026-09-25 5:44 ` Borislav Petkov
2026-09-29 3:26 ` Ryan Chen
2026-09-29 3:31 ` Borislav Petkov
2026-09-29 5:28 ` Ryan Chen
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=20260922031905.GEarHzqf56ypqALDHi@fat_crate.local \
--to=bp@alien8.de \
--cc=andrew@codeconstruct.com.au \
--cc=bp@suse.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=ryan_chen@aspeedtech.com \
--cc=sschaeck@cisco.com \
--cc=stable@vger.kernel.org \
--cc=tony.luck@intel.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