From: Dave Jiang <dave.jiang@intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: 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 13:47:27 -0700 [thread overview]
Message-ID: <1ec76ee6-87ef-45d2-bd60-41e2e1372e39@intel.com> (raw)
In-Reply-To: <20250307150434.GP354511@nvidia.com>
On 3/7/25 8:04 AM, Jason Gunthorpe wrote:
> On Fri, Mar 07, 2025 at 07:57:15PM +1100, Stephen Rothwell wrote:
>> Hi all,
>>
>> 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")
>
> Thanks Stephen,
>
> Dave can you fix all of thes kdoc bugs and post a new version?
>
After fixing up most of the issues, I cannot figure out what the issue is for this one:
./include/uapi/cxl/features.h:1: warning: no structured comments found
I'm not seeing any issues in the header via visual inspection. Running kernel_docs against the file yields no warning or error either. Deleting all the contents from that header file and I'm still seeing the warning. Makes no sense....
I'll repost the series on the mailing list with what I have fixed.
> Jason
next prev parent reply other threads:[~2025-03-07 20:47 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
2025-03-07 15:04 ` Jason Gunthorpe
2025-03-07 20:47 ` Dave Jiang [this message]
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=1ec76ee6-87ef-45d2-bd60-41e2e1372e39@intel.com \
--to=dave.jiang@intel.com \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).