netdev - Re: [PATCH v15 00/22] Type2 device basic 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: <8342ea50-ea07-4ae8-8607-be48936bcd11@amd.com>
Date: Tue, 13 May 2025 09:12:09 +0100
From: Alejandro Lucero Palau <alucerop@....com>
To: Dave Jiang <dave.jiang@...el.com>, alejandro.lucero-palau@....com,
 linux-cxl@...r.kernel.org, netdev@...r.kernel.org, dan.j.williams@...el.com,
 edward.cree@....com, davem@...emloft.net, kuba@...nel.org,
 pabeni@...hat.com, edumazet@...gle.com
Subject: Re: [PATCH v15 00/22] Type2 device basic support

On 5/12/25 23:36, Dave Jiang wrote:
>
> On 5/12/25 9:10 AM, alejandro.lucero-palau@....com wrote:
>> From: Alejandro Lucero <alucerop@....com>
>>
>> v15 changes:
>>   - remove reference to unused header file (Jonathan Cameron)
>>   - add proper kernel docs to exported functions (Alison Schofield)
>>   - using an array to map the enums to strings (Alison Schofield)
>>   - clarify comment when using bitmap_subset (Jonathan Cameron)
>>   - specify link to type2 support in all patches (Alison Schofield)
>>
>>    Patches changed (minor): 4, 11
>>
> Hi Alejandro,
> Tried to pull this series using b4. Noticed couple things.
> 1. Can you run checkpatch on the entire series and fix any issues?
> 2. Can you rebase against v6.15-rc4? I think there are some conflicts against the fixes went in rc4.
>
> Thanks!
>   

Hi Dave, I'm afraid I do not know what you mean with b4. Tempted to say 
it was a typo, but in any case, better if you can clarify.

The patchset is against the last cxl-next commit as it it stated at the 
end, and that is based on v6.15.0-rc4. I had to solve some issues from 
v14 as last changes in core/region.c from Robert Richter required so.

About checkpatch, I did so but I have just done it again for being sure 
before this email, and I do not seen any issue except a trailing space 
in patch 1. That same patch has also warnings I do not think are a 
problem. Some are related to moved code and other on the new macro. 
FWIW, I'm running those with "checkpatch --strict".

>>
>>
>> base-commit: a223ce195741ca4f1a0e1a44f3e75ce5662b6c06
>