LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Julian Brost <linux-kernel@0x4a42.net>
To: linux-doc@vger.kernel.org
Cc: Julian Brost <linux-kernel@0x4a42.net>,
	linux-kernel@vger.kernel.org, corbet@lwn.net,
	tomas.winkler@intel.com, linux-mei@linux.intel.com,
	linux-kernel@i4.cs.fau.de, fabian.hofmann@fau.de
Subject: [PATCH 4/4] Documentation/misc-devices/mei: Fix indentation of embedded code.
Date: Mon, 12 Jan 2015 00:58:09 +0100	[thread overview]
Message-ID: <1421020689-28332-5-git-send-email-linux-kernel@0x4a42.net> (raw)
In-Reply-To: <1421020689-28332-1-git-send-email-linux-kernel@0x4a42.net>

Some of the source code embedded in mei-client-bus.txt was indented
using spaces. This properly indents it with tabs and also removes a
single space that was placed in front of a closing curly brace.

Signed-off-by: Julian Brost <linux-kernel@0x4a42.net>
Signed-off-by: Fabian Hofmann <fabian.hofmann@fau.de>
---
 Documentation/misc-devices/mei/mei-client-bus.txt | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/Documentation/misc-devices/mei/mei-client-bus.txt b/Documentation/misc-devices/mei/mei-client-bus.txt
index 6ca486b..743be4e 100644
--- a/Documentation/misc-devices/mei/mei-client-bus.txt
+++ b/Documentation/misc-devices/mei/mei-client-bus.txt
@@ -72,11 +72,11 @@ static struct mei_cl_device_id contact_mei_cl_tbl[] = {
 MODULE_DEVICE_TABLE(mei_cl, contact_mei_cl_tbl);
 
 static struct mei_cl_driver contact_driver = {
-       .id_table = contact_mei_tbl,
-       .name = CONTACT_DRIVER_NAME,
+	.id_table = contact_mei_tbl,
+	.name = CONTACT_DRIVER_NAME,
 
-       .probe = contact_probe,
-       .remove = contact_remove,
+	.probe = contact_probe,
+	.remove = contact_remove,
 };
 
 static int contact_init(void)
@@ -112,7 +112,7 @@ int contact_probe(struct mei_cl_device *dev, struct mei_cl_device_id *id)
 	mei_cl_register_event_cb(dev, contact_event_cb, contact);
 
 	return 0;
- }
+}
 
 In the probe routine the driver first enable the MEI device and then registers
 an ME bus event handler which is as close as it can get to registering a
-- 
2.2.1


  parent reply	other threads:[~2015-01-11 23:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-11 23:58 [PATCH 0/4] Documentation/misc-devices/mei: Fix formatting Julian Brost
2015-01-11 23:58 ` [PATCH 1/4] Documentation/misc-devices/mei: Fix formatting of headings Julian Brost
2015-01-28 19:17   ` Jonathan Corbet
2015-01-29  1:39     ` [i4passt] " Alexander Wuerstlein
2015-01-29 19:57       ` Jonathan Corbet
2015-01-11 23:58 ` [PATCH 2/4] Documentation/misc-devices/mei: Fix spacing around parentheses Julian Brost
2015-01-11 23:58 ` [PATCH 3/4] Documentation/misc-devices/mei: Fix indentation of enumeration Julian Brost
2015-01-11 23:58 ` Julian Brost [this message]
2015-01-12  4:56   ` [PATCH 4/4] Documentation/misc-devices/mei: Fix indentation of embedded code Jeremiah Mahler
2015-01-12  4:57 ` [PATCH 0/4] Documentation/misc-devices/mei: Fix formatting Jeremiah Mahler
2015-01-12  8:55   ` Winkler, Tomas

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=1421020689-28332-5-git-send-email-linux-kernel@0x4a42.net \
    --to=linux-kernel@0x4a42.net \
    --cc=corbet@lwn.net \
    --cc=fabian.hofmann@fau.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@i4.cs.fau.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mei@linux.intel.com \
    --cc=tomas.winkler@intel.com \
    --subject='Re: [PATCH 4/4] Documentation/misc-devices/mei: Fix indentation of embedded code.' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).