From: Conor Dooley <conor.dooley@microchip.com>
To: Yixun Lan <dlan@gentoo.org>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Conor Dooley <conor@kernel.org>, Yangyu Chen <cyy@cyyself.name>,
Jisheng Zhang <jszhang@kernel.org>,
Jesse Taube <mr.bossman075@gmail.com>,
Inochi Amaoto <inochiama@outlook.com>,
Icenowy Zheng <uwu@icenowy.me>,
Meng Zhang <zhangmeng.kevin@spacemit.com>,
Meng Zhang <kevin.z.m@hotmail.com>, <soc@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v2] MAINTAINERS: setup support for SpacemiT SoC tree
Date: Thu, 19 Dec 2024 12:52:31 +0000 [thread overview]
Message-ID: <20241219-lumpish-reach-00c29cf962fa@wendy> (raw)
In-Reply-To: <173461125325.241921.7669060101424869020.b4-ty@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
On Thu, Dec 19, 2024 at 08:50:41PM +0800, Yixun Lan wrote:
>
> On Mon, 28 Oct 2024 07:04:00 +0800, Yixun Lan wrote:
> > Add myself as maintainer of SpacemiT's SoC tree, which
> > suggested by Conor [1].
> >
> >
>
> Thanks, Applied to SpacemiT's SoC tree:
> https://github.com/spacemit-com/linux/ (for-next)
>
> [1/1] MAINTAINERS: setup support for SpacemiT SoC tree
> commit: f187e72262c3245bc032a1a0f106784fb8562a0b
>
> The for-next branch will be sent via a formal Pull Request to
> the Linux SoC maintainers for inclusion in next merge window.
BTW, did you get your branches into linux-next yet? I forget if we
talked about this before (sorry).
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-12-19 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-27 23:04 Yixun Lan
2024-10-27 23:31 ` Yixun Lan
2024-12-19 12:50 ` Yixun Lan
2024-12-19 12:52 ` Conor Dooley [this message]
2024-12-19 13:55 ` 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=20241219-lumpish-reach-00c29cf962fa@wendy \
--to=conor.dooley@microchip.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor@kernel.org \
--cc=cyy@cyyself.name \
--cc=dlan@gentoo.org \
--cc=inochiama@outlook.com \
--cc=jszhang@kernel.org \
--cc=kevin.z.m@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mr.bossman075@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=soc@kernel.org \
--cc=uwu@icenowy.me \
--cc=zhangmeng.kevin@spacemit.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®