From: Yixun Lan <dlan@kernel.org>
To: Guodong Xu <docular.xu@gmail.com>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev, Alex Elder <elder@riscstar.com>
Subject: Re: [PATCH v2] MAINTAINERS: add entry for SpacemiT reset controller driver
Date: Thu, 10 Sep 2026 21:34:42 +0000 [thread overview]
Message-ID: <20260910213442-GKE2346@kernel.org> (raw)
In-Reply-To: <43ce274d284a4f94815ec25f5ca0604f.docular.xu@gmail.com>
Hi Guodong, Philipp,
On 10:09 Thu 10 Sep , Guodong Xu wrote:
> Hi Philipp,
>
> On 2026-08-07 19:51, Guodong Xu wrote:
> > On 2026-06-03 09:34, Philipp Zabel wrote:
> > [ ... ]
> > >Acked-by: Philipp Zabel <p.zabel@pengutronix.de>
> >
> > Gentle ping. All tags on this one are collected:
> >
> > Acked-by: Philipp Zabel <p.zabel@pengutronix.de>
> > Reviewed-by: Yixun Lan <dlan@kernel.org>
> > Acked-by: Alex Elder <elder@riscstar.com>
> >
> > Could you take it through the reset tree when convenient?
>
> Second ping. This is a MAINTAINERS-only change and carries your
> Acked-by, plus Reviewed-by from Yixun and Acked-by from Alex.
>
> If it is easier for you, I'd like to ask Yixun whether it could go
> through the SpacemiT SoC tree instead. Unless you object, I'd suggest
> we go that way if it has not been picked up by 2026-09-17.
>
Sounds a good plan, let's give Philipp some time to respond, if he still
unable to proceed by that time, then I will pick it.. just want to avoid
collision that both of us picked accidently..
--
Yixun Lan (dlan)
next prev parent reply other threads:[~2026-09-10 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 10:26 Guodong Xu
2026-06-03 7:34 ` Philipp Zabel
2026-08-07 23:51 ` Guodong Xu
2026-09-10 14:09 ` Guodong Xu
2026-09-10 21:34 ` Yixun Lan [this message]
2026-06-03 14:47 ` Yixun Lan
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=20260910213442-GKE2346@kernel.org \
--to=dlan@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=docular.xu@gmail.com \
--cc=elder@riscstar.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=spacemit@lists.linux.dev \
/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®