From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Matteo Martelli <matteomartelli3@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
<jic23@kernel.org>, <linux-iio@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the iio tree
Date: Tue, 29 Oct 2024 09:43:49 +0000 [thread overview]
Message-ID: <20241029094349.00001186@Huawei.com> (raw)
In-Reply-To: <20241029155022.5f777572@canb.auug.org.au>
On Tue, 29 Oct 2024 15:50:22 +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:555: warning: Function parameter or struct member 'read_avail_release_resource' not described in 'iio_info'
>
> Introduced by commit
>
> 8a63e3033e72 ("iio: core: add read_avail_release_resource callback to fix race")
>
Thanks. Sorry for number of times I've missed things this cycle!
Will fix this up when on right machine. Matteo, feel free to send a
patch if you have time, if not I'll make something suitable up.
Jonathan
next prev parent reply other threads:[~2024-10-29 9:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 4:50 linux-next: build warning after merge of the iio tree Stephen Rothwell
2024-10-29 9:43 ` 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-11-07 11:40 Stephen Rothwell
2024-11-07 12:25 ` 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=20241029094349.00001186@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=matteomartelli3@gmail.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;
as well as URLs for NNTP newsgroup(s).