From: Baohua.Song@csr.com (Barry Song)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] ARM: CSR: timer: space required before the open parenthesis '('
Date: Thu, 22 Sep 2011 22:51:29 -0700 [thread overview]
Message-ID: <1316757091-14916-3-git-send-email-Baohua.Song@csr.com> (raw)
In-Reply-To: <1316757091-14916-1-git-send-email-Baohua.Song@csr.com>
Signed-off-by: Barry Song <Baohua.Song@csr.com>
---
arch/arm/mach-prima2/timer.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-prima2/timer.c b/arch/arm/mach-prima2/timer.c
index 225ed3b..26ab6fe 100644
--- a/arch/arm/mach-prima2/timer.c
+++ b/arch/arm/mach-prima2/timer.c
@@ -140,7 +140,7 @@ unsigned long long notrace sched_clock(void)
* if we map timer memory in .init of sys_timer, system
* will panic due to illegal memory access
*/
- if(!is_mapped) {
+ if (!is_mapped) {
sirfsoc_of_timer_map();
is_mapped = 1;
}
--
1.7.1
Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom
More information can be found at www.csr.com. Follow CSR on Twitter at http://twitter.com/CSR_PLC and read our blog at www.csr.com/blog
next prev parent reply other threads:[~2011-09-23 5:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 5:51 [PATCH 0/4] ARM: CSR: cleanup some minor coding-style issues Barry Song
2011-09-23 5:51 ` [PATCH 1/4] ARM: CSR: timer: do not initialise statics to 0 or NULL Barry Song
2011-09-23 5:51 ` Barry Song [this message]
2011-09-23 5:51 ` [PATCH 3/4] ARM: CSR: prima2: fix trailing whitespace Barry Song
2011-09-23 5:51 ` [PATCH 4/4] ARM: CSR: clock: Fix indentation Barry Song
2011-09-30 19:56 ` [PATCH 0/4] ARM: CSR: cleanup some minor coding-style issues Arnd Bergmann
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=1316757091-14916-3-git-send-email-Baohua.Song@csr.com \
--to=baohua.song@csr.com \
--cc=linux-arm-kernel@lists.infradead.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