From: "Wu, Bryan" <bryan.wu@analog.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>, Paul Mundt <lethal@linux-sh.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH -mm] Blackfin arch: cleanup cache header file
Date: Mon, 26 Mar 2007 18:11:42 +0800 [thread overview]
Message-ID: <1174903902.32691.64.camel@roc-desktop> (raw)
Hi folks,
According to Paul's review, this patch cleanup the
include/asm-blackfin/cache.h comments.
Signed-off-by: Bryan Wu <bryan.wu@analog.com>
---
include/asm-blackfin/cache.h | 20 ++++++++++++++------
1 file changed, 14 insertions(+), 6 deletions(-)
Index: linux-2.6/include/asm-blackfin/cache.h
===================================================================
--- linux-2.6.orig/include/asm-blackfin/cache.h
+++ linux-2.6/include/asm-blackfin/cache.h
@@ -1,13 +1,21 @@
+/*
+ * include/asm-blackfin/cache.h
+ */
#ifndef __ARCH_BLACKFIN_CACHE_H
#define __ARCH_BLACKFIN_CACHE_H
-/* bytes per L1 cache line */
-#define L1_CACHE_SHIFT 5 /* BlackFin loads 32 bytes for cache */
-#define L1_CACHE_BYTES (1 << L1_CACHE_SHIFT)
+/*
+ * Bytes per L1 cache line
+ * Blackfin loads 32 bytes for cache
+ */
+#define L1_CACHE_SHIFT 5
+#define L1_CACHE_BYTES (1 << L1_CACHE_SHIFT)
-/* For speed we do need to align these ...MaTed---*/
-/* But include/linux/cache.h does this for us if we DO not define ...MaTed---*/
-#define __cacheline_aligned /***** maybe no need this Tony *****/
+/*
+ * Don't make __cacheline_aligned and
+ * ____cacheline_aligned defined in include/linux/cache.h
+ */
+#define __cacheline_aligned
#define ____cacheline_aligned
/*
_
Thanks
-Bryan
next reply other threads:[~2007-03-26 10:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 10:11 Wu, Bryan [this message]
2007-03-26 11:28 ` Paul Mundt
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=1174903902.32691.64.camel@roc-desktop \
--to=bryan.wu@analog.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome