linux-kernel - Re: linux-next: build warning after merge of the powerpc tree

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: <6d17f7d6-a508-4e81-bfaa-c8cf45a71a3e@linux.ibm.com>
Date: Wed, 19 Feb 2025 10:53:36 +0530
From: Madhavan Srinivasan <maddy@...ux.ibm.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
        Michael Ellerman <mpe@...erman.id.au>,
        PowerPC <linuxppc-dev@...ts.ozlabs.org>, martin.petersen@...cle.com
Cc: Andrew Donnellan <ajd@...ux.ibm.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the powerpc tree



On 2/19/25 10:16 AM, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the powerpc tree, today's linux-next build (htmldocs)
> produced this warning:
> 
> WARNING: Documentation/ABI/testing/sysfs-class-cxl not found
> 
> Introduced by commit
> 
>   5731d41af924 ("cxl: Deprecate driver")
> 
> The reference is from Documentation/arch/powerpc/cxl.rst
> 
> I don't know why this has appeared just now.

Ok IIUC, 

There is a 2 patch series to remove the cxl and cxlflash driver

https://lore.kernel.org/lkml/20250203072801.365551-1-ajd@linux.ibm.com/T/

Now Martin has already applied first patch (cxlflasg driver removal) in 
his staging tree

https://lore.kernel.org/lkml/20250203072801.365551-1-ajd@linux.ibm.com/T/#r8d7bb4c05256551cdcd6b7b563a8255409b07d70

Now, I was looking at applying the second patch in my tree,
But it is not apply cleanly and has dependency.

So Martin, I can send my Acked-by for the second patch, 
can you take the second patch also via your tree?
which will resolve the issue here 

Maddy
>