From: Peter Rosin <peda@axentia.se>
To: <linux-kernel@vger.kernel.org>
Cc: Peter Rosin <peda@axentia.se>, Wolfram Sang <wsa@the-dreams.de>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Jonathan Corbet <corbet@lwn.net>, <linux-i2c@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-iio@vger.kernel.org>,
<linux-doc@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH v9 01/10] devres: trivial whitespace fix
Date: Wed, 8 Feb 2017 16:41:48 +0100 [thread overview]
Message-ID: <1486568517-6997-2-git-send-email-peda@axentia.se> (raw)
In-Reply-To: <1486568517-6997-1-git-send-email-peda@axentia.se>
Everything else is indented with two spaces, so fix the odd one out.
Acked-by: Jonathan Cameron <jic23@kernel.org>
Signed-off-by: Peter Rosin <peda@axentia.se>
---
Documentation/driver-model/devres.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/driver-model/devres.txt b/Documentation/driver-model/devres.txt
index ca9d1eb46bc0..dc51fb024190 100644
--- a/Documentation/driver-model/devres.txt
+++ b/Documentation/driver-model/devres.txt
@@ -330,7 +330,7 @@ MEM
devm_kzalloc()
MFD
- devm_mfd_add_devices()
+ devm_mfd_add_devices()
PER-CPU MEM
devm_alloc_percpu()
--
2.1.4
next prev parent reply other threads:[~2017-02-08 15:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 15:41 [PATCH v9 00/10] mux controller abstraction and iio/i2c muxes Peter Rosin
2017-02-08 15:41 ` Peter Rosin [this message]
2017-02-08 15:41 ` [PATCH v9 02/10] dt-bindings: document devicetree bindings for mux-controllers and gpio-mux Peter Rosin
2017-02-08 15:41 ` [PATCH v9 03/10] mux: minimal mux subsystem and gpio-based mux controller Peter Rosin
2017-02-08 15:41 ` [PATCH v9 04/10] iio: inkern: api for manipulating ext_info of iio channels Peter Rosin
2017-02-08 15:41 ` [PATCH v9 05/10] dt-bindings: iio: io-channel-mux: document io-channel-mux bindings Peter Rosin
2017-02-08 15:41 ` [PATCH v9 06/10] iio: multiplexer: new iio category and iio-mux driver Peter Rosin
2017-02-08 15:41 ` [PATCH v9 07/10] dt-bindings: i2c: i2c-mux: document general purpose i2c-mux bindings Peter Rosin
2017-02-15 22:55 ` Rob Herring
2017-02-08 15:41 ` [PATCH v9 08/10] i2c: i2c-mux-gpmux: new driver Peter Rosin
2017-02-08 15:41 ` [PATCH v9 09/10] dt-bindings: mux-adg792a: document devicetree bindings for ADG792A/G mux Peter Rosin
2017-02-15 22:57 ` Rob Herring
2017-02-08 15:41 ` [PATCH v9 10/10] mux: adg792a: add mux controller driver for ADG792A/G Peter Rosin
2017-02-28 15:17 ` [PATCH v9 00/10] mux controller abstraction and iio/i2c muxes Peter Rosin
2017-02-28 17:18 ` Greg Kroah-Hartman
2017-03-03 15:30 ` Peter Rosin
2017-03-03 16:52 ` Wolfram Sang
2017-03-03 17:20 ` Jonathan Cameron
2017-03-03 18:44 ` Peter Rosin
2017-03-03 19:30 ` Wolfram Sang
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=1486568517-6997-2-git-send-email-peda@axentia.se \
--to=peda@axentia.se \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=wsa@the-dreams.de \
/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