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: <e7a8d7a7-b14e-12e7-76ea-64c4c20b3ddf@quicinc.com>
Date: Thu, 23 Oct 2025 11:00:09 +0530
From: Md Sadre Alam <quic_mdalam@...cinc.com>
To: Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
        Mark Brown
	<broonie@...nel.org>
CC: <robh@...nel.org>, <krzk+dt@...nel.org>, <conor+dt@...nel.org>,
        <andersson@...nel.org>, <konradybcio@...nel.org>, <vkoul@...nel.org>,
        <linux-arm-msm@...r.kernel.org>, <linux-spi@...r.kernel.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <dmaengine@...r.kernel.org>, <quic_varada@...cinc.com>
Subject: Re: [PATCH v3 1/9] spi: dt-bindings: spi-qpic-snand: Add IPQ5424
 compatible



On 10/22/2025 8:58 PM, Konrad Dybcio wrote:
> On 10/22/25 5:20 PM, Md Sadre Alam wrote:
>> Hi,
>>
>> On 10/22/2025 4:12 PM, Mark Brown wrote:
>>> On Wed, Oct 22, 2025 at 12:29:01PM +0530, Md Sadre Alam wrote:
>>>> On 10/22/2025 12:39 AM, Mark Brown wrote:
>>>>> On Tue, Oct 14, 2025 at 04:35:26PM +0530, Md Sadre Alam wrote:
>>>>>> IPQ5424 contains the QPIC-SPI-NAND flash controller which is the same as
>>>>>> the one found in IPQ9574. So let's document the IPQ5424 compatible and
>>>>>> use IPQ9574 as the fallback.
>>>
>>>>> This doesn't apply against current code, please check and resend.
>>>
>>>> Thank you for the feedback. I’d appreciate a bit more clarity on what
>>>> “doesn't apply against current code” refers to in this context. I’ve
>>>> manually applied the patch against the latest mainline (torvalds/linux) and
>>>> it applied cleanly without any conflicts. Please let me know if there’s a
>>>> specific tree or integration point I should be checking against.
>>>
>>> I tried to apply it to the spi tree
>>>
>>>     https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-6.19
>> Thanks for letting me know — I’ll rebase the patch on the SPI tree (for-6.19) and resend it.
> 
> JFYI you can generally count on linux-next/master as a good base
Thanks Konrad — noted! I’ll use linux-next/master as my base going forward.

Thanks,
Alam.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ