linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Jonathan Corbet <corbet@lwn.net>,
	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, 7 Nov 2024 12:25:00 +0000	[thread overview]
Message-ID: <20241107122500.00004628@Huawei.com> (raw)
In-Reply-To: <20241107224012.2981aa90@canb.auug.org.au>

On Thu, 7 Nov 2024 22:40:12 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi all,
> 
> After merging the iio tree, today's linux-next build (htmldocs) produced
> this warning:
> 
> include/linux/iio/iio.h:628: warning: Function parameter or struct member '__private' not described in 'iio_dev'
> include/linux/iio/iio.h:628: warning: Excess struct member 'priv' description in 'iio_dev'
> 
> Introduced by commit
> 
>   9a5a2483bc60 ("iio: Mark iio_dev::priv member with __private")
> 

I guess we need to teach the kernel-doc script about __private.
May be just a case of doing the same as done for __aligned, __packed etc.

Also curious why I've not seen warnings in the past about the masklength field
in the same structure.  I guess the test coverage has improved (or I missed
the reports!).

 So a 
   $members =~ s/\s*__private\s*\([^;]*\)/ /gos;

about here:
https://elixir.free-electrons.com/linux/v6.11.6/source/scripts/kernel-doc#L1148

Jon, does that make sense to you?  

Completely untested as I'm on wrong computer at the moment and my approach
to these scripts is cut and paste a similar smelling line until it works ;)

Jonathan





  reply	other threads:[~2024-11-07 12:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07 11:40 linux-next: build warning after merge of the iio tree Stephen Rothwell
2024-11-07 12:25 ` Jonathan Cameron [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-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-04-28  7:37 Stephen Rothwell
2022-04-28  8:07 ` Miquel Raynal
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=20241107122500.00004628@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=corbet@lwn.net \
    --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).