From: Conor Dooley <conor@kernel.org>
To: linux-kernel@vger.kernel.org, Conor Dooley <conor@kernel.org>
Cc: Conor Dooley <conor.dooley@microchip.com>,
Daire McNamara <daire.mcnamara@microchip.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 0/3] Add support for Microchip PIC64GX Curiosity Kit
Date: Tue, 3 Mar 2026 17:16:29 +0000 [thread overview]
Message-ID: <20260303-judicial-blissful-a6cf6282104f@spud> (raw)
In-Reply-To: <20251117-paprika-tipping-e7bb3e211d6f@spud>
From: Conor Dooley <conor.dooley@microchip.com>
On Mon, 17 Nov 2025 16:53:21 +0000, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> v3 of Pierre-Henry's stuff from over a year ago:
> https://lore.kernel.org/all/20240930095449.1813195-1-pierre-henry.moussay@microchip.com/
> In it he said "This will be fix in a V3 coming in due time", and I guess
> that due time was ~14 months.
>
> [...]
Applied to riscv-dt-for-next, thanks!
[1/3] dt-bindings: riscv: microchip: document the PIC64GX curiosity kit
https://git.kernel.org/conor/c/c8cbde5dc18b
[2/3] riscv: dts: microchip: add pic64gx and its curiosity kit
https://git.kernel.org/conor/c/a3c02b37a631
[3/3] riscv: dts: microchip: remove POLARFIRE mention in Makefile
https://git.kernel.org/conor/c/4eddc7ed4904
Thanks,
Conor.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: linux-kernel@vger.kernel.org, Conor Dooley <conor@kernel.org>
Cc: Conor Dooley <conor.dooley@microchip.com>,
Daire McNamara <daire.mcnamara@microchip.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 0/3] Add support for Microchip PIC64GX Curiosity Kit
Date: Tue, 3 Mar 2026 17:16:29 +0000 [thread overview]
Message-ID: <20260303-judicial-blissful-a6cf6282104f@spud> (raw)
In-Reply-To: <20251117-paprika-tipping-e7bb3e211d6f@spud>
From: Conor Dooley <conor.dooley@microchip.com>
On Mon, 17 Nov 2025 16:53:21 +0000, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> v3 of Pierre-Henry's stuff from over a year ago:
> https://lore.kernel.org/all/20240930095449.1813195-1-pierre-henry.moussay@microchip.com/
> In it he said "This will be fix in a V3 coming in due time", and I guess
> that due time was ~14 months.
>
> [...]
Applied to riscv-dt-for-next, thanks!
[1/3] dt-bindings: riscv: microchip: document the PIC64GX curiosity kit
https://git.kernel.org/conor/c/c8cbde5dc18b
[2/3] riscv: dts: microchip: add pic64gx and its curiosity kit
https://git.kernel.org/conor/c/a3c02b37a631
[3/3] riscv: dts: microchip: remove POLARFIRE mention in Makefile
https://git.kernel.org/conor/c/4eddc7ed4904
Thanks,
Conor.
next prev parent reply other threads:[~2026-03-03 17:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 16:53 [PATCH v3 0/3] Add support for Microchip PIC64GX Curiosity Kit Conor Dooley
2025-11-17 16:53 ` Conor Dooley
2025-11-17 16:53 ` [PATCH v3 1/3] dt-bindings: riscv: microchip: document the PIC64GX curiosity kit Conor Dooley
2025-11-17 16:53 ` Conor Dooley
2025-11-17 21:48 ` Rob Herring (Arm)
2025-11-17 21:48 ` Rob Herring (Arm)
2025-11-17 16:53 ` [PATCH v3 2/3] riscv: dts: microchip: add pic64gx and its " Conor Dooley
2025-11-17 16:53 ` Conor Dooley
2025-11-17 16:53 ` [PATCH v3 3/3] riscv: dts: microchip: remove POLARFIRE mention in Makefile Conor Dooley
2025-11-17 16:53 ` Conor Dooley
2026-03-03 17:16 ` Conor Dooley [this message]
2026-03-03 17:16 ` [PATCH v3 0/3] Add support for Microchip PIC64GX Curiosity Kit Conor Dooley
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=20260303-judicial-blissful-a6cf6282104f@spud \
--to=conor@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=robh@kernel.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.