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: <b6035539-efb9-4491-8822-59e8a2a5ad04@oss.qualcomm.com>
Date: Mon, 12 Jan 2026 11:13:52 +0800
From: Yijie Yang <yijie.yang@....qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
        Krzysztof Kozlowski <krzk@...nel.org>, andersson@...nel.org,
        konradybcio@...nel.org, robh@...nel.org, krzk+dt@...nel.org,
        conor+dt@...nel.org
Cc: linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
        devicetree@...r.kernel.org, krzysztof.kozlowski@....qualcomm.com
Subject: Re: [PATCH v2 0/4] Initial patch set for PURWA-IOT-EVK



On 1/9/2026 5:28 PM, Konrad Dybcio wrote:
> On 1/9/26 9:26 AM, Yijie Yang wrote:
>>
>>
>> On 1/9/2026 4:06 PM, Krzysztof Kozlowski wrote:
>>> On 09/01/2026 08:59, YijieYang wrote:
>>>>
>>>> Signed-off-by: Yijie Yang <yijie.yang@....qualcomm.com>
>>>> ---
>>>> Changes since V1:
>>>> - Update the GPU firmware path.
>>>> - Update the description in the cover letter.
>>>> - Reorder the patches.
>>>> - Use separate DTS files for Purwa and Hamoa.
>>>> - Update base commit.
>>>
>>> That's a b4 patchset, so where are the links?
>>
>> Sorry about that. I generated the patch set using git format-patch with format control options for easier review, while creating the cover letter with b4. Since the version number does not increase automatically, the change list was written manually, and I missed adding the link to v1. I will include it in the following versions.
> 
> Adding
> 
> [diff]
>          renameLimit = 999999
> 	algorithm = patience
> 
> to your .gitconfig should work too (perhaps comment it out after
> you're done sending a largely copy-and-alter-a-big-file patchset
> like this)

That sounds like a good solution—thanks for the reminder.

> 
> Konrad

-- 
Best Regards,
Yijie


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ