linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Guan Xuetao" <gxt@mprc.pku.edu.cn>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: about __BITS_PER_LONG
Date: Mon, 11 Apr 2011 15:34:55 +0800	[thread overview]
Message-ID: <003f01cbf81a$f48cfdf0$dda6f9d0$@mprc.pku.edu.cn> (raw)

Hi, Arnd:

  When using asm-generic/bitsperlong.h, I think that __BITS_PER_LONG could be the
same as BITS_PER_LONG if-not-defined. And this could avoid the duplicated macros
in almost all architectures.

Regards.

Guan Xuetao

---
diff --git a/include/asm-generic/bitsperlong.h b/include/asm-generic/bitsperlong.h
index 4ae54e0..31d032a 100644
--- a/include/asm-generic/bitsperlong.h
+++ b/include/asm-generic/bitsperlong.h
@@ -9,7 +9,11 @@
  * to decide it, but rather check a compiler provided macro.
  */
 #ifndef __BITS_PER_LONG
-#define __BITS_PER_LONG 32
+#   ifdef CONFIG_64BIT
+#	define __BITS_PER_LONG 64
+#   else
+#	define __BITS_PER_LONG 32
+#   endif /* CONFIG_64BIT */
 #endif
 
 #ifdef __KERNEL__

             reply	other threads:[~2011-04-11  7:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-11  7:34 Guan Xuetao [this message]
2011-04-11  7:34 ` about __BITS_PER_LONG Guan Xuetao
2011-04-11 15:24 ` Arnd Bergmann
2011-04-12  1:24   ` Guan Xuetao

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='003f01cbf81a$f48cfdf0$dda6f9d0$@mprc.pku.edu.cn' \
    --to=gxt@mprc.pku.edu.cn \
    --cc=arnd@arndb.de \
    --cc=linux-arch@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).