From: Ragner Magalhaes <ragner.magalhaes@indt.org.br>
To: linux-omap-open-source@linux.omap.com
Subject: [PATCH] Fixing cpu_class_is_omap2() parentheses warning
Date: Mon, 25 Jun 2007 14:22:49 -0400 [thread overview]
Message-ID: <20070625182249.19564.42233.stgit@localhost.localdomain> (raw)
From: Ragner Magalhaes <ragner.magalhaes@indt.org.br>
Fixing the follow warning
arch/arm/plat-omap/usb.c: In function 'omap_usb0_init':
arch/arm/plat-omap/usb.c:136: warning: suggest parentheses around && within ||
Signed-off-by: Ragner Magalhaes <ragner.magalhaes@indt.org.br>
---
include/asm-arm/arch-omap/cpu.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/asm-arm/arch-omap/cpu.h b/include/asm-arm/arch-omap/cpu.h
index 4eea68b..b9399a8 100644
--- a/include/asm-arm/arch-omap/cpu.h
+++ b/include/asm-arm/arch-omap/cpu.h
@@ -273,6 +273,6 @@ IS_OMAP_TYPE(3430, 0x3430)
/* Macros to detect if we have OMAP1 or OMAP2 */
#define cpu_class_is_omap1() (cpu_is_omap730() || cpu_is_omap15xx() || \
cpu_is_omap16xx())
-#define cpu_class_is_omap2() cpu_is_omap24xx() || cpu_is_omap34xx()
+#define cpu_class_is_omap2() (cpu_is_omap24xx() || cpu_is_omap34xx())
#endif
next reply other threads:[~2007-06-25 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 18:22 Ragner Magalhaes [this message]
2007-06-29 7:21 ` [PATCH] Fixing cpu_class_is_omap2() parentheses warning Tony Lindgren
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=20070625182249.19564.42233.stgit@localhost.localdomain \
--to=ragner.magalhaes@indt.org.br \
--cc=linux-omap-open-source@linux.omap.com \
/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