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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <4f836d88-80a7-402b-9af0-f0d002e2145d@app.fastmail.com>
Date: Mon, 21 Jul 2025 16:31:37 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@...aro.org>,
 "Harshit Shah" <hshah@...ado.com>, "Rob Herring" <robh@...nel.org>,
 "Krzysztof Kozlowski" <krzk+dt@...nel.org>,
 "Conor Dooley" <conor+dt@...nel.org>,
 "Linus Walleij" <linus.walleij@...aro.org>,
 "Bartosz Golaszewski" <brgl@...ev.pl>,
 "Catalin Marinas" <catalin.marinas@....com>, "Will Deacon" <will@...nel.org>,
 "Jan Kotas" <jank@...ence.com>,
 "Greg Kroah-Hartman" <gregkh@...uxfoundation.org>,
 "Jiri Slaby" <jirislaby@...nel.org>, "Michal Simek" <michal.simek@....com>,
 Przemysław Gaj <pgaj@...ence.com>,
 "Alexandre Belloni" <alexandre.belloni@...tlin.com>,
 "Frank Li" <Frank.Li@....com>,
 "'bbrezillon@...nel.org'" <bbrezillon@...nel.org>
Cc: "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
 "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>,
 "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
 "soc@...ts.linux.dev" <soc@...ts.linux.dev>,
 "linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>,
 "linux-i3c@...ts.infradead.org" <linux-i3c@...ts.infradead.org>
Subject: Re: [PATCH v6 00/10] Axiado AX3000 SoC and Evaluation Board Support

On Sun, Jul 20, 2025, at 14:09, Krzysztof Kozlowski wrote:
> On 19/07/2025 03:09, Harshit Shah wrote:
>> On 7/17/2025 11:14 PM, Krzysztof Kozlowski wrote:
>> 
>> It mentions about the special case where "Introducing a completely new 
>> SoC platform." we can submit patches to soc@...nel.org directly.
>> 
>> However I see two different points in the doc.
>> 
>> 1. Submitting patches directly to soc@...nel.org with email
>> 
>> 2. There is also mention about the "Branches and Pull requests"
>> 
>> (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/maintainer-soc.rst?h=v6.16-rc1#n186). 
>> 
>> 
>> I think if we need to use this approach then we need to create a new 
>> branch on soc and create a pull request based on the same. (with the soc 
>> tree[1])
>
> You do not create branches on other poeple's trees (like soc). You
> create branch on your own tree.

Yes, ideally the base should be -rc1, as for any other pull request.

> You can go with 1 or 2, up to you, I don't know which one is preferred
> by Arnd for new boards.

Separate patches (1) tend to work better for the first contribution
from a new maintainer, since there is less to know in advance.

      Arnd

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ