From: Jason Gunthorpe <jgg@nvidia.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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 19:25:19 -0400 [thread overview]
Message-ID: <20250307232519.GA470898@nvidia.com> (raw)
In-Reply-To: <1ec76ee6-87ef-45d2-bd60-41e2e1372e39@intel.com>
> 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
It is because of this:
Documentation/userspace-api/fwctl/fwctl-cxl.rst:.. kernel-doc:: include/uapi/cxl/features.h
Which includes the file and as the message says there are not kdoc
comments in the file.
I'll squish this into your v8:
--- a/Documentation/userspace-api/fwctl/fwctl-cxl.rst
+++ b/Documentation/userspace-api/fwctl/fwctl-cxl.rst
@@ -39,7 +39,6 @@ fwctl cxl User API
==================
.. kernel-doc:: include/uapi/fwctl/cxl.h
-.. kernel-doc:: include/uapi/cxl/features.h
1. Driver info query
--------------------
Jason
next prev parent reply other threads:[~2025-03-07 23:25 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
2025-03-07 23:25 ` Jason Gunthorpe [this message]
-- 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=20250307232519.GA470898@nvidia.com \
--to=jgg@nvidia.com \
--cc=dave.jiang@intel.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