From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Lechner <dlechner@baylibre.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Andreas Klinger <ak@it-klinger.de>
Subject: Re: linux-next: build warning after merge of the iio tree
Date: Tue, 20 Aug 2024 10:08:43 +0100 [thread overview]
Message-ID: <20240820100843.00003b77@Huawei.com> (raw)
In-Reply-To: <20240820134739.50c771cb@canb.auug.org.au>
On Tue, 20 Aug 2024 13:47:39 +1000
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> After merging the iio tree, today's linux-next build (htmldocs) produced
> this warning:
>
> Warning: /sys/bus/iio/devices/iio:deviceX/in_resistance_calibbias is defined 2 times: Documentation/ABI/testing/sysfs-bus-iio-chemical-sgp40:18 Documentation/ABI/testing/sysfs-bus-iio:541
>
> Introduced by commit
>
> 0f718e10da81 ("iio: ABI: add missing calibbias attributes")
Thanks.
I think it's a case of just deleting the sgp40 version.
We will loose a bit of information, but I don't think it's critical
info to be worth a special chunk in the main docs.
Jonathan
>
next prev parent reply other threads:[~2024-08-20 9:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 3:47 linux-next: build warning after merge of the iio tree Stephen Rothwell
2024-08-20 9:08 ` 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-29 4:50 Stephen Rothwell
2024-10-29 9:43 ` Jonathan Cameron
2024-10-15 4:50 Stephen Rothwell
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=20240820100843.00003b77@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=ak@it-klinger.de \
--cc=dlechner@baylibre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.