From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Lothar Rubusch <l.rubusch@gmail.com>,
Andy Shevchenko <andy@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 iio tree
Date: Mon, 14 Jul 2025 11:18:21 +0300 [thread overview]
Message-ID: <aHS9TZWsKThHilpQ@smile.fi.intel.com> (raw)
In-Reply-To: <20250714181341.1d10df2a@canb.auug.org.au>
On Mon, Jul 14, 2025 at 06:13:41PM +1000, Stephen Rothwell wrote:
>
> After merging the iio tree, today's linux-next build (htmldocs) produced
> these warnings:
>
> Documentation/iio/adxl313.rst:230: ERROR: Error in "code-block" directive:
> maximum 1 argument(s) allowed, 11 supplied.
>
> .. code-block:: bash
+ blank line here should fix it I think.
Same for the rest.
> root:/sys/bus/iio/devices/iio:device0> echo 1.28125 > ./events/in_accel_mag_rising_value
> root:/sys/bus/iio/devices/iio:device0> echo 1 > ./events/in_accel_x\|y\|z_mag_rising_en
>
> root:/sys/bus/iio/devices/iio:device0> iio_event_monitor adxl313
> Found IIO device with name adxl313 with device number 0
> <only while moving the sensor>
> Event: time: 1748795762298351281, type: accel(x|y|z), channel: 0, evtype: mag, direction: rising
> Event: time: 1748795762302653704, type: accel(x|y|z), channel: 0, evtype: mag, direction: rising
> Event: time: 1748795762304340726, type: accel(x|y|z), channel: 0, evtype: mag, direction: rising
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-07-14 8:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 8:13 linux-next: build warnings after merge of the iio tree Stephen Rothwell
2025-07-14 8:18 ` Andy Shevchenko [this message]
2025-07-14 18:20 ` Jonathan Cameron
-- strict thread matches above, loose matches on Subject: below --
2024-10-22 5:08 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=aHS9TZWsKThHilpQ@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=andy@kernel.org \
--cc=l.rubusch@gmail.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.