Andes Voyager board patches for v6.17

The following changes since commit 0bb71d301869446810a0b13d3da290bd455d7c78:

Add linux-next specific files for 20250612 (2025-06-12 14:07:02 +1000)

are available in the Git repository at:

[email protected]:ben717-linux/linux.git tags/andes-newsoc-6.17

for you to fetch changes up to 8909a9795ed9991e9ed12d7bf21c9648b2c2f22f:

riscv: dts: andes: add Voyager board device tree (2025-06-12 15:45:26 +0800)

----------------------------------------------------------------
Andes Voyager board patches for v6.17

The patchset [1] for the Andes Voyager board (including the Andes QiLai SoC) has been tested on the latest linux-next/master branch and reviewed on the relevant mailing lists.

[1] https://lore.kernel.org/all/[email protected]/

----------------------------------------------------------------
Ben Zong-You Xie (7):
riscv: add Andes SoC family Kconfig support
dt-bindings: riscv: add Andes QiLai SoC and the Voyager board bindings
dt-bindings: interrupt-controller: add Andes QiLai PLIC
dt-bindings: interrupt-controller: add Andes machine-level software interrupt controller
dt-bindings: timer: add Andes machine timer
riscv: dts: andes: add QiLai SoC device tree
riscv: dts: andes: add Voyager board device tree

 Documentation/devicetree/bindings/interrupt-controller/andestech,plicsw.yaml  |  54 +++++++++++++++++
 Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml |   1 +
 Documentation/devicetree/bindings/riscv/andes.yaml                            |  25 ++++++++
 Documentation/devicetree/bindings/timer/andestech,plmt0.yaml                  |  53 +++++++++++++++++
 MAINTAINERS                                                                   |   9 +++
 arch/riscv/Kconfig.errata                                                     |   2 +-
 arch/riscv/Kconfig.socs                                                       |   9 +++
 arch/riscv/boot/dts/Makefile                                                  |   1 +
 arch/riscv/boot/dts/andes/Makefile                                            |   2 +
 arch/riscv/boot/dts/andes/qilai-voyager.dts                                   |  28 +++++++++
 arch/riscv/boot/dts/andes/qilai.dtsi                                          | 186 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 11 files changed, 369 insertions(+), 1 deletion(-)
 create mode 100644 Documentation/devicetree/bindings/interrupt-controller/andestech,plicsw.yaml
 create mode 100644 Documentation/devicetree/bindings/riscv/andes.yaml
 create mode 100644 Documentation/devicetree/bindings/timer/andestech,plmt0.yaml
 create mode 100644 arch/riscv/boot/dts/andes/Makefile
 create mode 100644 arch/riscv/boot/dts/andes/qilai-voyager.dts
 create mode 100644 arch/riscv/boot/dts/andes/qilai.dtsi

Hi Ben,

Thanks for your submission. I see that Conor has been guiding you so far, but there are still a number of small mistakes here, so I won't pull this version.

I'll reply here in more detail than normal, so you can get things right for the next submission:

1. Your branch is based on linux-next, which means it cannot be merged cleanly into mainline because of the thousands of other patches that are now on your branch. I recommend to always use -rc1 as the base for new work.
2. If you have a git tree with your work, it makes sense to have that in linux-next directly, but that can probably wait until after the initial merge so your name shows up in the MAINTAINERS file. Once that is there, you can email Stephen Rothwell and ask him to add your git URL
3. The github.com URL is not one I can pull from, please use an https:// URL next time. You can configure separate 'url' and 'pushurl' settings in your .git/config in order to have 'git request-pull' get the right one
4. Once you are in the maintainers file, you can ask for a kernel.org account and publish your branch there, this is usually preferred over github.
5. I see that you have signed the commit with your gpg key, which is good, but I have not been able to download this key from any known keyserver. Can please upload it somewhere and let me know so I can fetch it. Is the key already signed by someone on the kernel keyring?
6. The email text in the pull request has overly long lines, as 'git request-pull' tries to use the entire width of your terminal window. The easiest way to avoid this is to redirect the git command into a file, to get the default 80 character line length. I personally use
'git request-pull ... | xclip' to put it into the clipboard.

To make things easier, maybe just send the contents of the pull request as patches to [email protected] this time, then you don't have to figure it all out at once.

Arnd