linux-kernel - Re: [PATCH] docs: iio: Fix unexpected indentation for adxl345.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250825104016.0cc2ac2d@jic23-huawei>
Date: Mon, 25 Aug 2025 10:40:16 +0100
From: Jonathan Cameron <jic23@...nel.org>
To: Jonathan Cameron <Jonathan.Cameron@...wei.com>
Cc: Xing Guo <higuoxing@...il.com>, <sfr@...b.auug.org.au>,
 <l.rubusch@...il.com>, <linux-kernel@...r.kernel.org>,
 <linux-next@...r.kernel.org>, <shuah@...nel.org>,
 <linux-iio@...r.kernel.org>
Subject: Re: [PATCH] docs: iio: Fix unexpected indentation for adxl345.

On Fri, 22 Aug 2025 10:37:18 +0100
Jonathan Cameron <Jonathan.Cameron@...wei.com> wrote:

> On Tue, 19 Aug 2025 14:56:34 +0800
> Xing Guo <higuoxing@...il.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@...b.auug.org.au>
> > Closes: https://lore.kernel.org/linux-next/20250818124124.5b978e64@canb.auug.org.au
> > Signed-off-by: Xing Guo <higuoxing@...il.com>  
> 
> +CC linux-iio.
Applied.  Thanks,

> 
> > ---
> >  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.  
> 
>