public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
	Dan Williams <dan.j.williams@intel•com>
Cc: 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 07:53:33 -0700	[thread overview]
Message-ID: <19a4ee38-9777-4efc-bffe-13d5a2c2f003@intel.com> (raw)
In-Reply-To: <20250715185737.5d9c75e4@canb.auug.org.au>



On 7/15/25 1:57 AM, Stephen Rothwell wrote:
> 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 :-) ).
> 
No worries. Should be fixed in the next linux-next pull. 

  parent reply	other threads:[~2025-07-15 14:53 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
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   ` Dave Jiang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-05  5:17 linux-next: build failure after merge of the cxl tree 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=19a4ee38-9777-4efc-bffe-13d5a2c2f003@intel.com \
    --to=dave.jiang@intel$(echo .)com \
    --cc=dan.j.williams@intel$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=rrichter@amd$(echo .)com \
    --cc=sfr@canb$(echo .)auug.org.au \
    /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