From: Matt Porter <mporter@kernel.crashing.org>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org, linuxppc-embedded@ozlabs.org
Subject: [PATCH][RIO] -mm: Fix macro indenting
Date: Mon, 6 Jun 2005 16:52:21 -0700 [thread overview]
Message-ID: <1118101941657@foobar.com> (raw)
In-Reply-To: mporter@kernel.crashing.org
Fix up indenting that Lindent fubared.
Signed-off-by: Matt Porter <mporter@kernel.crashing.org
commit 87ff3372a005e4cf927b1b62c23e1c2339d46507
tree 16e1d9454a95a4a1e8b9e50dacd218f8e14dfe14
parent 6e9e41d480cf54c69d47df11f5cba696461ebe1a
author Matt Porter <mporter@kernel.crashing.org> Mon, 06 Jun 2005 09:23:49 -0700
committer Matt Porter <mporter@kernel.crashing.org> Mon, 06 Jun 2005 09:23:49 -0700
drivers/rio/rio-access.c | 24 ++++++++++++------------
1 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/drivers/rio/rio-access.c b/drivers/rio/rio-access.c
--- a/drivers/rio/rio-access.c
+++ b/drivers/rio/rio-access.c
@@ -77,13 +77,13 @@ int __rio_local_write_config_##size \
}
RIO_LOP_READ(8, u8, 1)
- RIO_LOP_READ(16, u16, 2)
- RIO_LOP_READ(32, u32, 4)
- RIO_LOP_WRITE(8, u8, 1)
- RIO_LOP_WRITE(16, u16, 2)
- RIO_LOP_WRITE(32, u32, 4)
+RIO_LOP_READ(16, u16, 2)
+RIO_LOP_READ(32, u32, 4)
+RIO_LOP_WRITE(8, u8, 1)
+RIO_LOP_WRITE(16, u16, 2)
+RIO_LOP_WRITE(32, u32, 4)
- EXPORT_SYMBOL(__rio_local_read_config_8);
+EXPORT_SYMBOL(__rio_local_read_config_8);
EXPORT_SYMBOL(__rio_local_read_config_16);
EXPORT_SYMBOL(__rio_local_read_config_32);
EXPORT_SYMBOL(__rio_local_write_config_8);
@@ -137,13 +137,13 @@ int rio_mport_write_config_##size \
}
RIO_OP_READ(8, u8, 1)
- RIO_OP_READ(16, u16, 2)
- RIO_OP_READ(32, u32, 4)
- RIO_OP_WRITE(8, u8, 1)
- RIO_OP_WRITE(16, u16, 2)
- RIO_OP_WRITE(32, u32, 4)
+RIO_OP_READ(16, u16, 2)
+RIO_OP_READ(32, u32, 4)
+RIO_OP_WRITE(8, u8, 1)
+RIO_OP_WRITE(16, u16, 2)
+RIO_OP_WRITE(32, u32, 4)
- EXPORT_SYMBOL(rio_mport_read_config_8);
+EXPORT_SYMBOL(rio_mport_read_config_8);
EXPORT_SYMBOL(rio_mport_read_config_16);
EXPORT_SYMBOL(rio_mport_read_config_32);
EXPORT_SYMBOL(rio_mport_write_config_8);
next reply other threads:[~2005-06-06 23:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 23:52 Matt Porter [this message]
2005-06-06 23:52 ` [PATCH][RIO] -mm: Convert EXPORT_SYMBOL -> EXPORT_SYMBOL_GPL Matt Porter
2005-06-06 23:52 ` [PATCH][RIO] -mm: sysfs config space fixes Matt Porter
2005-06-06 23:52 ` [PATCH][RIO] -mm: ppc32 EXPORT_SYMBOL_GPL conversions Matt Porter
2005-06-06 23:52 ` [PATCH][RIO] -mm: rionet updates Matt Porter
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=1118101941657@foobar.com \
--to=mporter@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).