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: <82e1cebd-2101-4d9c-9de2-c3b54fc3a3fa@linaro.org>
Date: Sat, 30 Aug 2025 11:12:56 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Harshit Shah <hshah@...ado.com>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, Arnd Bergmann <arnd@...db.de>,
 "soc@...ts.linux.dev" <soc@...ts.linux.dev>, "soc@...nel.org"
 <soc@...nel.org>
Cc: "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
 "linux-arm-kernel@...ts.infradead.org"
 <linux-arm-kernel@...ts.infradead.org>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] arm64: dts: axiado: Add missing UART aliases

On 29/08/2025 20:17, Harshit Shah wrote:
> On 8/28/2025 10:58 PM, Krzysztof Kozlowski wrote:
>> Please don't do this. It just generates unnecessary traffic. See my
>> instructions you receive on your first submissions.... unless you want
>> to send patches to soc@ (which looks added here) but then this is also
> 
> Hi Krzysztof,
> 
> Yes, the reason I have resent this patch with adding (soc@) as this is 
> the fix from the previous series.
> 
> Fixes: 1f7055779001 ("arm64: dts: axiado: Add initial support for AX3000 SoC and eval board")
> 
> I missed to add those aliases and it is giving probe failures without 
> these changes. So I was hoping if this could be merged as the fix
> 
> in the upcoming -rcX before the next merge window.
The goal is correct, but you need to follow standard soc-subsystem
maintainer process. You need to have your tree in the next, then collect
the patches and fixes to respective branches, and then send multiple of
them in pull request or as patches ONLY to soc@.

My Beginners maintainer talk from LPC 23 might help you.

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ