From: Conor Dooley <conor@kernel.org>
To: jixincheng@ultrarisc.com
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>, Andrew Lunn <andrew@lunn.ch>,
Jia Wang <wangjia@ultrarisc.com>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
Thomas Gleixner <tglx@kernel.org>,
Samuel Holland <samuel.holland@sifive.com>,
Anup Patel <anup@brainfault.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@sifive.com>,
linux-riscv@lists.infradead.org,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v8 0/8] riscv: Add device tree support for UltraRISC DP1000
Date: Thu, 12 Nov 2026 18:01:48 +0000 [thread overview]
Message-ID: <20261112-legend-outcast-c2226b5e02a1@spud> (raw)
In-Reply-To: <20261112-ultrarisc-dts-v8-0-14fa0834cac4@ultrarisc.com>
[-- Attachment #1: Type: text/plain, Size: 1323 bytes --]
On Thu, Nov 12, 2026 at 10:00:59AM +0800, Xincheng Ji via B4 Relay wrote:
> base-commit: 704340f1cd0dcef829eb62f5b48ae95a2ce17bdf
> change-id: 20260522-ultrarisc-dts-9dab3a2316b6
> prerequisite-message-id: <20260907-dwmac-ultrarisc-v2-0-9a39bf8db313@ultrarisc.com>
> prerequisite-patch-id: 92e6cf1352d54e283d7721dc1542b580b8a41be1
> prerequisite-patch-id: 875c2058e9d8a983d785d7447374758f994dc847
> prerequisite-patch-id: 060a9b129c32c623a52ab1ba66f7a357e54575ff
> prerequisite-patch-id: 9aafbac6d2531a378b2057bf57787c814523f9d3
> prerequisite-patch-id: d75120a112276bd966d37441bd4d631e1539d0e8
> prerequisite-patch-id: f526d36e1a4adb659a812fd4145dca2e69b19453
> prerequisite-patch-id: 7d5e12085468dba34526d9047c62b357f874f91e
I applied the set.
Please do not include this prerequisite-patch-id stuff in the future,
none of it is actually required for this series as far as I can tell and
even if it was, I couldn't apply any of them anyway since they don't
belong to my tree.
I squashed the maintainers patch, since it didn't make sense to add it
incorrectly and then replace it.
There's a bunch more maintainers entries with your former colleague in
them for the dp1000 so you should probably also update all of those.
Perhaps it would be wise to have more than one maintainer in case you
leave too!
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-11-12 18:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 2:00 Xincheng Ji via B4 Relay
2026-11-12 2:01 ` [PATCH v8 1/8] dt-bindings: vendor-prefixes: Add shenrongda Xincheng Ji via B4 Relay
2026-11-12 2:01 ` [PATCH v8 2/8] dt-bindings: riscv: cpus: Add UltraRISC CP100 compatible Xincheng Ji via B4 Relay
2026-11-12 2:01 ` [PATCH v8 3/8] dt-bindings: riscv: Add UltraRISC DP1000 board compatibles Xincheng Ji via B4 Relay
2026-11-12 2:01 ` [PATCH v8 4/8] dt-bindings: timer: Add UltraRISC DP1000 CLINT Xincheng Ji via B4 Relay
2026-11-12 2:01 ` [PATCH v8 5/8] riscv: dts: ultrarisc: Add initial device tree for UltraRISC DP1000 Xincheng Ji via B4 Relay
2026-11-12 2:01 ` [PATCH v8 6/8] riscv: dts: ultrarisc: Add Shenzhen Rongda M0 board device tree Xincheng Ji via B4 Relay
2026-11-12 2:01 ` [PATCH v8 7/8] riscv: dts: ultrarisc: Add Milk-V Titan " Xincheng Ji via B4 Relay
2026-11-12 2:01 ` [PATCH v8 8/8] MAINTAINERS: Update UltraRISC platform maintainer and tree Xincheng Ji via B4 Relay
2026-11-12 18:01 ` Conor Dooley [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=20261112-legend-outcast-c2226b5e02a1@spud \
--to=conor@kernel.org \
--cc=alex@ghiti.fr \
--cc=andrew@lunn.ch \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=daniel.lezcano@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jixincheng@ultrarisc.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=tglx@kernel.org \
--cc=wangjia@ultrarisc.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®