From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Dan Williams <dan.j.williams@intel•com>
Cc: Dave Jiang <dave.jiang@intel•com>,
Robert Richter <rrichter@amd•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the cxl tree
Date: Tue, 15 Jul 2025 18:57:37 +1000 [thread overview]
Message-ID: <20250715185737.5d9c75e4@canb.auug.org.au> (raw)
In-Reply-To: <20250715184935.7e7c75c0@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 513 bytes --]
Hi all,
On Tue, 15 Jul 2025 18:49:35 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> After merging the cxl tree, today's linux-next build (htmldocs) failed
> like this:
>
> drivers/cxl/cxl.h:443: warning: Function parameter or struct member 'cache_size' not described in 'cxl_root_decoder'
>
> Caused by commit
>
> 8d41af0d378d ("cxl: Remove core/acpi.c and cxl core dependency on ACPI")
This is only a warning (I ran the wrong helper script :-) ).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-07-15 8:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 8:49 linux-next: build failure after merge of the cxl tree Stephen Rothwell
2025-07-15 8:57 ` Stephen Rothwell [this message]
2025-07-15 10:40 ` [PATCH v2] cxl: Remove core/acpi.c and cxl core dependency on ACPI Robert Richter
2025-07-15 14:53 ` linux-next: build failure after merge of the cxl tree Dave Jiang
-- strict thread matches above, loose matches on Subject: below --
2024-01-05 5:17 Stephen Rothwell
2024-01-06 3:23 ` Dan Williams
2021-09-06 4:20 Stephen Rothwell
2021-09-07 17:43 ` Dan Williams
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=20250715185737.5d9c75e4@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dan.j.williams@intel$(echo .)com \
--cc=dave.jiang@intel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rrichter@amd$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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