linux-kernel - Re: [PATCH v5 0/8] add Voyager board support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aEmrHPd7RxUSOLAY@atctrx.andestech.com>
Date: Thu, 12 Jun 2025 00:13:16 +0800
From: Ben Zong-You Xie <ben717@...estech.com>
To: Conor Dooley <conor@...nel.org>
CC: <paul.walmsley@...ive.com>, <palmer@...belt.com>, <aou@...s.berkeley.edu>,
        <alex@...ti.fr>, <robh@...nel.org>, <krzk+dt@...nel.org>,
        <conor+dt@...nel.org>, <tglx@...utronix.de>,
        <daniel.lezcano@...aro.org>, <prabhakar.mahadev-lad.rj@...renesas.com>,
        <devicetree@...r.kernel.org>, <linux-riscv@...ts.infradead.org>,
        <linux-kernel@...r.kernel.org>, <tim609@...estech.com>
Subject: Re: [PATCH v5 0/8] add Voyager board support

On Mon, Jun 09, 2025 at 05:17:50PM +0100, Conor Dooley wrote:
> [EXTERNAL MAIL]

> Date: Mon, 9 Jun 2025 17:17:50 +0100
> From: Conor Dooley <conor@...nel.org>
> To: Ben Zong-You Xie <ben717@...estech.com>
> Cc: paul.walmsley@...ive.com, palmer@...belt.com, aou@...s.berkeley.edu,
>  alex@...ti.fr, robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
>  tglx@...utronix.de, daniel.lezcano@...aro.org,
>  prabhakar.mahadev-lad.rj@...renesas.com, devicetree@...r.kernel.org,
>  linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
>  tim609@...estech.com
> Subject: Re: [PATCH v5 0/8] add Voyager board support
> 
> On Mon, Jun 09, 2025 at 05:16:54PM +0100, Conor Dooley wrote:
> > On Mon, Jun 09, 2025 at 08:06:07PM +0800, Ben Zong-You Xie wrote:
> > > On Fri, Jun 06, 2025 at 05:00:06PM +0100, Conor Dooley wrote:
> > > > [EXTERNAL MAIL]
> > > 
> > > > Date: Fri, 6 Jun 2025 17:00:06 +0100
> > > > From: Conor Dooley <conor@...nel.org>
> > > > To: Ben Zong-You Xie <ben717@...estech.com>
> > > > Cc: paul.walmsley@...ive.com, palmer@...belt.com, aou@...s.berkeley.edu,
> > > >  alex@...ti.fr, robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
> > > >  tglx@...utronix.de, daniel.lezcano@...aro.org,
> > > >  prabhakar.mahadev-lad.rj@...renesas.com, devicetree@...r.kernel.org,
> > > >  linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
> > > >  tim609@...estech.com
> > > > Subject: Re: [PATCH v5 0/8] add Voyager board support
> > > > 
> > > > On Mon, Jun 02, 2025 at 02:07:39PM +0800, Ben Zong-You Xie wrote:
> > > > > The Voyager is a 9.6” x 9.6” Micro ATX form factor development board
> > > > > including Andes QiLai SoC. This patch series adds minimal device tree
> > > > > files for the QiLai SoC and the Voyager board [1].
> > > > > 
> > > > > Now only support basic uart drivers to boot up into a basic console. Other
> > > > > features will be added later.
> > > > > 
> > > > > [1] https://www.andestech.com/en/products-solutions/andeshape-platforms/qilai-chip/
> > > > 
> > > > Ball is in your court now, after rc1 make a tree and get it in
> > > > linux-next, and then send a pr to soc@...nel.org with this new content.
> > > > Perhaps the defconfig should go separately, I can take that one if you
> > > > want.
> > > > 
> > > > Cheers,
> > > > Conor.
> > > 
> > > Hi Conor,
> > > 
> > > Thanks for your guidance on these patches. I will send a PR to
> > > soc@...nel.org as you suggested.
> > > 
> > > For the defconfig patch, I'm happy for you to handle it. Just let me
> > > know if there's anything specific you'd like me to include.
> > 
> > Okay, I picked it up on the basis that you'll send this all to Arnd for
> > 6.17
> 
> Sorry, I think that was really poorly worded. I picked it up on the
> basis that you're going to send the other patches in the series to Arnd
> for 6.17.

Hi Conor,

According to the SoC maintainer documentation [1], I should send a
patchset (not a PR) to soc@...nel.org. Since I'm not a submaintainer yet.
I think I should not sent a PR to the main SoC maintainer. Is that right?

Further, I have two questions about sending a patchset:   
1. Should I send v5 or start a new patchset?
2. Should I continue excluding the defconfig patch, as we discussed
   previously? I think it should be included now.

[1] https://docs.kernel.org/process/maintainer-soc.html#submitting-patches-to-the-main-soc-maintainers

Thanks,
Ben