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] [day] [month] [year] [list]
Message-ID: <121d4e01-00cd-4be5-acbb-b140188048c3@linaro.org>
Date: Thu, 24 Apr 2025 08:17:51 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Deepti Jaggi <quic_djaggi@...cinc.com>, andersson@...nel.org,
 konradybcio@...nel.org, robh@...nel.org, krzk+dt@...nel.org,
 conor+dt@...nel.org
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org, quic_ptalari@...cinc.com,
 quic_psodagud@...cinc.com, quic_shazhuss@...cinc.com
Subject: Re: [PATCH v3] dt-bindings: arm: qcom: add SA8255p Ride board

On 24/04/2025 01:54, Deepti Jaggi wrote:
> 
> On 4/23/25 05:00, Krzysztof Kozlowski wrote:
>> On 23/04/2025 02:38, Deepti Jaggi wrote:
>>> From: Nikunj Kela <quic_nkela@...cinc.com>
>>>
>>> Document the SA8255p SoC and its reference board: sa8255p-ride.
>>>
>>> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
>>> Signed-off-by: Nikunj Kela <quic_nkela@...cinc.com>
>>> Signed-off-by: Deepti Jaggi <quic_djaggi@...cinc.com>
>>> ---
>>> Changes in v3:
>>> 	Removed the patches from original series[1]
>>
>> Why? This makes no sense on its own. Binding goes with the user. No
>> user? No binding.
> 
> Thanks for taking the time to review the patch.
> All the bindings that were initially included in the original series [1]
> were removed and posted as individual patches.
> devicetree has been posted as a separate patch :
> Link: https://lore.kernel.org/all/20250422231249.871995-1-quic_djaggi@quicinc.com
> If necessary, I can consolidate the bindings and dt into a single series
> for the next version.
I asked why and that's not the answer to why. That's description of what
you did, but we see it here. Anyway, I explained you the process.

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ