From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Michael Ellerman <mpe@ellerman.id.au>,
PowerPC <linuxppc-dev@lists.ozlabs.org>,
martin.petersen@oracle.com
Cc: Andrew Donnellan <ajd@linux.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the powerpc tree
Date: Wed, 19 Feb 2025 10:53:36 +0530 [thread overview]
Message-ID: <6d17f7d6-a508-4e81-bfaa-c8cf45a71a3e@linux.ibm.com> (raw)
In-Reply-To: <20250219154649.49986660@canb.auug.org.au>
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
>
next prev parent reply other threads:[~2025-02-19 5:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 4:46 linux-next: build warning after merge of the powerpc tree Stephen Rothwell
2025-02-19 5:23 ` Madhavan Srinivasan [this message]
2025-02-19 5:49 ` Andrew Donnellan
-- strict thread matches above, loose matches on Subject: below --
2025-05-13 10:28 Stephen Rothwell
2025-05-29 23:44 ` Stephen Rothwell
2025-05-30 13:10 ` Athira Rajeev
2025-04-29 8:57 Stephen Rothwell
2025-04-29 8:17 Stephen Rothwell
2024-11-20 6:13 Stephen Rothwell
2024-05-15 6:37 Stephen Rothwell
2024-05-16 2:42 ` Michael Ellerman
2024-05-16 4:36 ` Stephen Rothwell
2023-02-16 3:40 Stephen Rothwell
2023-02-16 18:06 ` Josh Poimboeuf
2023-02-17 1:35 ` Michael Ellerman
2023-02-17 7:05 ` Josh Poimboeuf
2021-08-23 9:55 Stephen Rothwell
2021-08-23 10:48 ` Stephen Rothwell
2021-08-23 14:19 ` Jonathan Corbet
2021-08-23 23:21 ` Stephen Rothwell
2021-08-24 5:18 ` Aneesh Kumar K.V
2021-08-24 13:46 ` Jonathan Corbet
2021-04-15 8:52 Stephen Rothwell
2021-04-16 10:54 ` Michael Ellerman
2021-04-14 23:36 Stephen Rothwell
2019-11-13 22:34 Stephen Rothwell
2017-09-04 8:53 Stephen Rothwell
2017-09-04 8:59 ` Cédric Le Goater
2015-10-20 5:21 Stephen Rothwell
2015-10-20 10:06 ` Michael Ellerman
2015-10-20 20:45 ` Stephen Rothwell
2011-05-19 3:19 Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6d17f7d6-a508-4e81-bfaa-c8cf45a71a3e@linux.ibm.com \
--to=maddy@linux.ibm.com \
--cc=ajd@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=martin.petersen@oracle.com \
--cc=mpe@ellerman.id.au \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).