From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jason Gunthorpe <jgg@nvidia•com>
Cc: Dave Jiang <dave.jiang@intel•com>, Jason Gunthorpe <jgg@ziepe•ca>,
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 hmm tree
Date: Fri, 7 Mar 2025 20:28:03 +1100 [thread overview]
Message-ID: <20250307202803.5cc8ce0c@canb.auug.org.au> (raw)
In-Reply-To: <20250307195715.0b7abf0f@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 474 bytes --]
Hi all,
On Fri, 7 Mar 2025 19:57:15 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> After merging the hmm tree, today's linux-next build (htmldocs) produced
> this warning:
>
> Error: Cannot open file /home/sfr/next/next/drivers/cxl/features.c
>
> Introduced by commit
>
> da0dd17604d4 ("fwctl/cxl: Add documentation to FWCTL CXL")
Also:
include/uapi/cxl/features.h:1: warning: no structured comments found
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-03-07 9:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 8:57 linux-next: build warning after merge of the hmm tree Stephen Rothwell
2025-03-07 9:28 ` Stephen Rothwell [this message]
2025-03-07 15:04 ` Jason Gunthorpe
2025-03-07 20:47 ` Dave Jiang
2025-03-07 23:25 ` Jason Gunthorpe
-- strict thread matches above, loose matches on Subject: below --
2025-03-07 9:13 Stephen Rothwell
2025-03-07 9:31 Stephen Rothwell
2025-03-18 10:39 Stephen Rothwell
2025-03-18 11:09 ` Jason Gunthorpe
2025-03-18 16:38 ` Nelson, Shannon
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=20250307202803.5cc8ce0c@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dave.jiang@intel$(echo .)com \
--cc=jgg@nvidia$(echo .)com \
--cc=jgg@ziepe$(echo .)ca \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/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