mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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>
Subject: Re: [PATCH v5 0/9] Add Aspeed AST2700 SDRAM EDAC support
Date: Thu, 22 Oct 2026 12:08:21 -0700	[thread overview]
Message-ID: <20261022190821.GAatpfJYsT2fqKhk3T@fat_crate.local> (raw)
In-Reply-To: <TY2PPF5CB9A1BE6C09C55652B1A6AA68725F2652@TY2PPF5CB9A1BE6.apcprd06.prod.outlook.com>

On Thu, Oct 22, 2026 at 09:52:36AM +0000, Ryan Chen wrote:
> Hello Boris,
> 	Just a gentle ping on this series.
> 	Any feedback would be appreciated.
> 	Please let me know if there is anything I should address or revise.

Lemme give you the spiel since you're new :)

From: Documentation/process/maintainer-tip.rst

Merge window
^^^^^^^^^^^^

Please do not expect large patch series to be handled during the merge
window or even during the week before.  Such patches should be submitted in
mergeable state *at* *least* a week before the merge window opens.
Exceptions are made for bug fixes and *sometimes* for small standalone
drivers for new hardware or minimally invasive patches for hardware
enablement.

During the merge window, the maintainers instead focus on following the
upstream changes, fixing merge window fallout, collecting bug fixes, and
allowing themselves a breath. Please respect that.

The release candidate -rc1 is the starting point for new patches to be
applied which are targeted for the next merge window.

---

While you're waiting, you could read

https://docs.kernel.org/process/submitting-patches.html
https://docs.kernel.org/process/development-process.html

and you could even help out and review some patches yourself. That would be
the most awesome help you could give to folks, and it would be very much
appreciated by maintainers who are drowning in patches.

Thanks.

-- 
Regards/Gruss,
    Boris.

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

  reply	other threads:[~2026-10-22 19:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07  6:13 Ryan Chen
2026-10-07  6:13 ` [PATCH v5 1/9] EDAC/aspeed: Set the DIMM grain Ryan Chen
2026-10-07  6:13 ` [PATCH v5 2/9] EDAC/aspeed: Free the interrupt before the mem_ctl_info on remove Ryan Chen
2026-10-07  6:13 ` [PATCH v5 3/9] EDAC/aspeed: Clean up whitespace and include ordering Ryan Chen
2026-10-07  6:13 ` [PATCH v5 4/9] EDAC/aspeed: Free the mem_ctl_info unconditionally on remove Ryan Chen
2026-10-07  6:13 ` [PATCH v5 5/9] dt-bindings: edac: aspeed: Add AST2700 SDRAM EDAC Ryan Chen
2026-10-07  6:13 ` [PATCH v5 6/9] EDAC/aspeed: Replace regmap with direct register access Ryan Chen
2026-11-05  4:56   ` Borislav Petkov
2026-10-07  6:13 ` [PATCH v5 7/9] EDAC/aspeed: Abstract SoC differences behind chip data Ryan Chen
2026-10-07  6:13 ` [PATCH v5 8/9] EDAC/aspeed: Add AST2700 support Ryan Chen
2026-10-07  6:13 ` [PATCH v5 9/9] MAINTAINERS: Step down as Aspeed AST2500 EDAC driver maintainer Ryan Chen
2026-10-07 20:32   ` Rob Herring (Arm)
2026-10-22  9:52 ` [PATCH v5 0/9] Add Aspeed AST2700 SDRAM EDAC support Ryan Chen
2026-10-22 19:08   ` Borislav Petkov [this message]
2026-10-22 23:53     ` 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=20261022190821.GAatpfJYsT2fqKhk3T@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=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

all inboxes | Powered by JetHome®