From: Yixun Lan <dlan@kernel.org>
To: Hung-Chun Tseng <alan.tseng.cs@gmail.com>
Cc: Eric Chung <eric.chung@riscstar.com>,
Tom Rini <trini@konsulko.com>,
Raymond Mao <raymond.mao@riscstar.com>,
u-boot-spacemit@groups.io, u-boot@lists.u-boot-project.org
Subject: Re: [PATCH] MAINTAINERS: spacemit: k1: add Hung-Chun Tseng as reviewer
Date: Tue, 17 Nov 2026 10:59:38 +0000 [thread overview]
Message-ID: <20261117105938-GKE100890@kernel.org> (raw)
In-Reply-To: <20261117003237.3090023-1-alan.tseng.cs@gmail.com>
Hi Hung-Chun Tseng,
On 08:32 Tue 17 Nov , Hung-Chun Tseng wrote:
> I test K1 patches on a Milk-V Jupiter and would like to help review
> them.
>
Avoid using first-person grammer? prefer imperative mood, I think U-Boot
follow similar rule as Linux Kernel or check doc/develop/sending_patches.rst
You can adjust as something like:
Add Hung-Chun Tseng as reviewer for SpacemiT K1 SoC.. blah..
> Signed-off-by: Hung-Chun Tseng <alan.tseng.cs@gmail.com>
> ---
> Applies on top of "MAINTAINERS: spacemit: k1: drop Huan Zhou".
>
> board/spacemit/k1/MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/board/spacemit/k1/MAINTAINERS b/board/spacemit/k1/MAINTAINERS
> index 93a5aa6677a..3fd97fb6ffd 100644
> --- a/board/spacemit/k1/MAINTAINERS
> +++ b/board/spacemit/k1/MAINTAINERS
> @@ -1,5 +1,6 @@
> BananaPi F3
> M: Eric Chung <eric.chung@riscstar.com>
> +R: Hung-Chun Tseng <alan.tseng.cs@gmail.com>
> L: u-boot-spacemit@groups.io
> S: Maintained
> F: arch/riscv/dts/k1-*-u-boot.dtsi
>
> base-commit: 83b1ec64ede9998566e6a82b22848c20a33f4aff
> prerequisite-patch-id: 974bda77e7d5815be9f750da8c47c9d5cd1eb15a
> --
> 2.56.1
>
--
Yixun Lan (dlan)
next prev parent reply other threads:[~2026-11-17 10:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 0:32 [PATCH] MAINTAINERS: spacemit: k1: add Hung-Chun Tseng as reviewer Hung-Chun Tseng
2026-11-17 10:59 ` Yixun Lan [this message]
2026-11-17 23:12 ` [PATCH v2] " Hung-Chun Tseng
2026-11-18 5:57 ` Yixun Lan
2026-11-18 6:17 ` 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=20261117105938-GKE100890@kernel.org \
--to=dlan@kernel.org \
--cc=alan.tseng.cs@gmail.com \
--cc=eric.chung@riscstar.com \
--cc=raymond.mao@riscstar.com \
--cc=trini@konsulko.com \
--cc=u-boot-spacemit@groups.io \
--cc=u-boot@lists.u-boot-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.