From: patchwork-bot+linux-riscv@kernel.org
To: Inochi Amaoto <inochiama@outlook.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
unicorn_wang@outlook.com, conor@kernel.org, chao.wei@sophgo.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] MAINTAINERS: Setup proper info for SOPHGO vendor support
Date: Mon, 25 Mar 2024 04:42:34 +0000 [thread overview]
Message-ID: <171134175480.18749.10483414416084336702.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <IA1PR20MB4953B158F6F575840F3D4267BB7D2@IA1PR20MB4953.namprd20.prod.outlook.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Inochi Amaoto <inochiama@outlook.com>:
On Tue, 30 Jan 2024 09:40:42 +0800 you wrote:
> Add git tree that maintaines sophgo vendor code.
> Also replace Chao Wei with myself, since he does not have enough time.
> Since sophgo vendor code is maintained, remove itself from
> `RISC-V MISC SOC`
>
> Signed-off-by: Inochi Amaoto <inochiama@outlook.com>
> Acked-by: Chao Wei <chao.wei@sophgo.com>
>
> [...]
Here is the summary with links:
- [v2] MAINTAINERS: Setup proper info for SOPHGO vendor support
https://git.kernel.org/riscv/c/0f46e1339ef1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2024-03-25 4:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 1:40 [PATCH v2] MAINTAINERS: Setup proper info for SOPHGO vendor support Inochi Amaoto
2024-01-30 2:03 ` Chen Wang
2024-01-31 14:39 ` Conor Dooley
2024-02-23 6:22 ` Inochi Amaoto
2024-03-25 4:42 ` patchwork-bot+linux-riscv [this message]
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=171134175480.18749.10483414416084336702.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=chao.wei@sophgo.com \
--cc=conor@kernel.org \
--cc=inochiama@outlook.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=unicorn_wang@outlook.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