linux-kernel - Re: [PATCH 15/41] Documentation: dt: mfd: fix spelling mistakes

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160425165830.GP2713@dell>
Date:	Mon, 25 Apr 2016 17:58:30 +0100
From:	Lee Jones <lee.jones@...aro.org>
To:	Rob Herring <robh@...nel.org>
Cc:	Eric Engestrom <eric@...estrom.ch>, linux-kernel@...r.kernel.org,
	Pawel Moll <pawel.moll@....com>,
	Mark Rutland <mark.rutland@....com>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	Kumar Gala <galak@...eaurora.org>, devicetree@...r.kernel.org
Subject: Re: [PATCH 15/41] Documentation: dt: mfd: fix spelling mistakes

On Mon, 25 Apr 2016, Rob Herring wrote:

> On Mon, Apr 25, 2016 at 01:24:12AM +0100, Eric Engestrom wrote:
> > Signed-off-by: Eric Engestrom <eric@...estrom.ch>
> 
> Applied, thanks.

I'd prefer to continue taking these if you don't mind Rob.  It'd limit
on the amount of immutable branch pull requests I have to send/handle.

> > ---
> >  Documentation/devicetree/bindings/mfd/qcom-rpm.txt | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/Documentation/devicetree/bindings/mfd/qcom-rpm.txt b/Documentation/devicetree/bindings/mfd/qcom-rpm.txt
> > index 5e97a95..b98b291 100644
> > --- a/Documentation/devicetree/bindings/mfd/qcom-rpm.txt
> > +++ b/Documentation/devicetree/bindings/mfd/qcom-rpm.txt
> > @@ -178,7 +178,7 @@ see regulator.txt - with additional custom properties described below:
> >  - qcom,force-mode:
> >  	Usage: optional (default if no other qcom,force-mode is specified)
> >  	Value type: <u32>
> > -	Defintion: indicates that the regulator should be forced to a
> > +	Definition: indicates that the regulator should be forced to a
> >  		   particular mode, valid values are:
> >  		   QCOM_RPM_FORCE_MODE_NONE - do not force any mode
> >  		   QCOM_RPM_FORCE_MODE_LPM - force into low power mode
> > @@ -204,7 +204,7 @@ see regulator.txt - with additional custom properties described below:
> >  - qcom,force-mode:
> >  	Usage: optional
> >  	Value type: <u32>
> > -	Defintion: indicates that the regulator should not be forced to any
> > +	Definition: indicates that the regulator should not be forced to any
> >  		   particular mode, valid values are:
> >  		   QCOM_RPM_FORCE_MODE_NONE - do not force any mode
> >  		   QCOM_RPM_FORCE_MODE_LPM - force into low power mode

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog