linux-kernel - Re: [PATCH v6 00/10] Axiado AX3000 SoC and Evaluation 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: <06f00d05-b8ca-41fa-9e5e-9cee3cfcfae1@axiado.com>
Date: Sat, 19 Jul 2025 01:09:32 +0000
From: Harshit Shah <hshah@...ado.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>, 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>, Arnd Bergmann <arnd@...db.de>, 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>, Boris Brezillon
	<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>, "linux-gpio@...r.kernel.org"
	<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 7/17/2025 11:14 PM, Krzysztof Kozlowski wrote:
>> Hi all,
>>
>> This patch series was reviewed by Krzysztof, and I am wondering if it’s
>> queued for the next merge window. Thanks in advance!
> It's not, unless you received clear notice about it. Please read
> maintainer soc profile how to send patches for merging.

Thank you Krzysztof for the reference.

We went through maintainer-soc.rst 
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/maintainer-soc.rst?h=v6.16-rc1#n73) 


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])


We are not sure if we should follow which method for this purpose. Can 
you please help on the same? Apologies for too long questions.


[1] https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git/

Regards,

Harshit.