netdev - Re: [PATCH v4 00/26] cxl: add Type2 device 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: <86522c97-350c-9319-6930-01f97a490578@amd.com>
Date: Wed, 23 Oct 2024 10:38:21 +0100
From: Alejandro Lucero Palau <alucerop@....com>
To: Paolo Abeni <pabeni@...hat.com>, alejandro.lucero-palau@....com,
 linux-cxl@...r.kernel.org, netdev@...r.kernel.org, dan.j.williams@...el.com,
 martin.habets@...inx.com, edward.cree@....com, davem@...emloft.net,
 kuba@...nel.org, edumazet@...gle.com
Subject: Re: [PATCH v4 00/26] cxl: add Type2 device support


On 10/23/24 09:46, Paolo Abeni wrote:
> Hi,
>
> 10/17/24 18:51, alejandro.lucero-palau@....com wrote:
>> 2) The driver for using the added functionality is not a test driver but a real
>> one: the SFC ethernet network driver. It uses the CXL region mapped for PIO
>> buffers instead of regions inside PCIe BARs.
> I'm sorry for the late feedback, but which is the merge plan here?
>
> The series spawns across 2 different subsystems and could cause conflicts.
>
> Could the network device change be separated and send (to netdev) after
> the clx ones land into Linus' tree?


Hi Paolo,


With v4 all sfc changes are different patches than those modifying CXL 
core, so I guess this is good for what you suggest.


Not sure the implications for merging only some patches into the CXL tree.


Thanks,

Alejandro


> Thanks,
>
> Paolo
>