From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Xing Guo <higuoxing@gmail.com>
Cc: <sfr@canb.auug.org.au>, <l.rubusch@gmail.com>,
<linux-kernel@vger.kernel.org>, <linux-next@vger.kernel.org>,
<shuah@kernel.org>, <linux-iio@vger.kernel.org>
Subject: Re: [PATCH] docs: iio: Fix unexpected indentation for adxl345.
Date: Fri, 22 Aug 2025 10:37:18 +0100 [thread overview]
Message-ID: <20250822103718.000062e1@huawei.com> (raw)
In-Reply-To: <20250819065634.1154322-1-higuoxing@gmail.com>
On Tue, 19 Aug 2025 14:56:34 +0800
Xing Guo <higuoxing@gmail.com> wrote:
> Resolved the following building error:
>
> Documentation/iio/adxl345.rst:161: ERROR: Unexpected indentation. [docutils]
>
> Fixes: fdcb9cb9178a ("docs: iio: add documentation for adxl345 driver")
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Closes: https://lore.kernel.org/linux-next/20250818124124.5b978e64@canb.auug.org.au
> Signed-off-by: Xing Guo <higuoxing@gmail.com>
+CC linux-iio.
> ---
> Documentation/iio/adxl345.rst | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/iio/adxl345.rst b/Documentation/iio/adxl345.rst
> index 4bd038cb4a37..afdb35f8b72e 100644
> --- a/Documentation/iio/adxl345.rst
> +++ b/Documentation/iio/adxl345.rst
> @@ -157,6 +157,7 @@ sensor terms, free-fall is defined using an inactivity period ranging from 0.000
> to 1.000 seconds.
>
> The driver behaves as follows:
> +
> * If the configured inactivity period is 1 second or more, the driver uses the
> sensor's inactivity register. This allows the event to be linked with
> activity detection, use auto-sleep, and be either AC- or DC-coupled.
next prev parent reply other threads:[~2025-08-22 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 2:41 linux-next: build warning after merge of the iio tree Stephen Rothwell
2025-08-19 6:56 ` [PATCH] docs: iio: Fix unexpected indentation for adxl345 Xing Guo
2025-08-22 9:37 ` Jonathan Cameron [this message]
2025-08-25 9:40 ` Jonathan Cameron
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=20250822103718.000062e1@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=higuoxing@gmail.com \
--cc=l.rubusch@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=shuah@kernel.org \
/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