linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jonathan Cameron <Jonathan.Cameron@Huawei.com>,
	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 iio tree
Date: Thu, 28 Apr 2022 10:07:19 +0200	[thread overview]
Message-ID: <20220428100719.4a29e68f@xps13> (raw)
In-Reply-To: <20220428173758.2e642f54@canb.auug.org.au>

Hello,

sfr@canb.auug.org.au wrote on Thu, 28 Apr 2022 17:37:58 +1000:

> Hi all,
> 
> After merging the iio tree, today's linux-next build (htmldocs) produced
> this warning:
> 
> include/linux/iio/iio.h:319: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
>  * Device operating modes
> 
> Introduced by commit
> 
>   831d87089ca8 ("iio: core: Clarify the modes")

Looks like there is no kdoc specific format for #define's
(Documentation/doc-guide/kernel-doc.rst), which is disappointing, I
really hoped this could be brought to the developer's attention this
way.

But that's not a big deal. Jonathan, if you don't mind, you may just
drop that extra start s|/**|/*| to make the htmldocs target happy
again.

Thanks,
Miquèl

  reply	other threads:[~2022-04-28  8:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28  7:37 linux-next: build warning after merge of the iio tree Stephen Rothwell
2022-04-28  8:07 ` Miquel Raynal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-18  2:41 Stephen Rothwell
2025-04-15  6:28 Stephen Rothwell
2025-04-15  7:35 ` Angelo Dureghello
2024-11-07 11:40 Stephen Rothwell
2024-11-07 12:25 ` Jonathan Cameron
2024-10-29  4:50 Stephen Rothwell
2024-10-29  9:43 ` Jonathan Cameron
2024-10-15  4:50 Stephen Rothwell
2024-08-20  3:47 Stephen Rothwell
2024-08-20  9:08 ` Jonathan Cameron
2024-06-05  3:34 Stephen Rothwell
2024-02-28  3:51 Stephen Rothwell
2022-07-01  5:29 Stephen Rothwell
2022-07-01  8:28 ` Stephen Rothwell
2022-07-01  9:28   ` Jonathan Cameron
2022-07-01 10:43   ` Jonathan Cameron
2022-02-11  7:42 Stephen Rothwell

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=20220428100719.4a29e68f@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=Jonathan.Cameron@Huawei.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).