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] [day] [month] [year] [list]

Message-Id: <f09dc88e-68b1-44dc-9761-724e64d1a5f1@app.fastmail.com>
Date: Thu, 03 Jul 2025 18:42:37 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Conor Dooley" <conor@...nel.org>
Cc: "Ben Zong-You Xie" <ben717@...estech.com>,
 "Paul Walmsley" <paul.walmsley@...ive.com>,
 "Palmer Dabbelt" <palmer@...belt.com>, "Albert Ou" <aou@...s.berkeley.edu>,
 "Alexandre Ghiti" <alex@...ti.fr>, "Rob Herring" <robh@...nel.org>,
 krzk+dt@...nel.org, "Conor Dooley" <conor+dt@...nel.org>,
 "Thomas Gleixner" <tglx@...utronix.de>,
 "Daniel Lezcano" <daniel.lezcano@...aro.org>,
 "Lad, Prabhakar" <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 Thu, Jul 3, 2025, at 17:53, Conor Dooley wrote:
> On Thu, Jul 03, 2025 at 05:32:08PM +0200, Arnd Bergmann wrote:
>> On Wed, Jun 11, 2025, at 18:21, Conor Dooley wrote:
>>
>> I'm also planning to have multiple new SoC targets in 6.17 and
>> would put them into a separate branch that does not contain the
>> dts changes for the existing SoCs.
>> 
>> For the pull request that Ben sent, there were a couple of
>> mistakes, I'll reply on that separately. It probably would made
>> more sense to send the patches to soc@...ts.linux.dev (note
>> that the soc@...nel.org address got renamed but they still
>> both work) than to send a pull request this time.
>
> Is that a general comment btw? If there are other people coming in with
> new platforms should I ask them to send patches to soc@...ts.linux.dev
> instead of a PR for their first time?

It's mainly about how comfortable the new maintainers are with
the process, in this case it was clearly a bit too much for
Ben to get right at the first time, but others are more
experienced with sending pull requests to kernel maintainers
already. Since the patches individually are all fine, I could
have just applied them, but the PR ended up having too many
mistakes.

The one thing that is special for a new platform is that the branch
can mix things that would otherwise be separate pull requests.
Sending this as patches means that I have more flexibility to
apply it either into a branch for the new platform or split it
up as normal.

    Arnd