From: Johannes Berg <johannes@sipsolutions.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Kalle Valo <kvalo@kernel.org>
Cc: Aditya Kumar Singh <quic_adisi@quicinc.com>,
Wireless <linux-wireless@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the wireless-next tree
Date: Mon, 09 Sep 2024 10:57:29 +0200 [thread overview]
Message-ID: <dac6bfc0a0d5b92fdcb0d330d5e4839d2e119154.camel@sipsolutions.net> (raw)
In-Reply-To: <20240909183924.73c3c91d@canb.auug.org.au>
On Mon, 2024-09-09 at 18:39 +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the wireless-next tree, today's linux-next build (htmldocs)
> produced these warnings:
>
> next/Documentation/driver-api/80211/cfg80211:14: next/include/net/cfg80211.h:6219: WARNING: Inline strong start-string without end-string.
> next/Documentation/driver-api/80211/cfg80211:14: next/include/net/cfg80211.h:6219: WARNING: Inline strong start-string without end-string.
> next/Documentation/driver-api/80211/cfg80211:14: next/include/net/cfg80211.h:6219: WARNING: Inline strong start-string without end-string.
>
> Introduced by commit
>
> 62c16f219a73 ("wifi: cfg80211: move DFS related members to links[] in wireless_dev")
>
Thanks for the report. kernel-doc htmldocs isn't part of the process I
usually do.
I don't even really know what this means, but I'll try to figure out a
way to fix it. Looks like it's due to the @ references there, which I'm
not sure are correct anyway, so I guess I'll just remove those.
johannes
prev parent reply other threads:[~2024-09-09 9:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 8:39 linux-next: build warnings after merge of the wireless-next tree Stephen Rothwell
2024-09-09 8:57 ` Johannes Berg [this message]
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=dac6bfc0a0d5b92fdcb0d330d5e4839d2e119154.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_adisi@quicinc.com \
--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