From: "tip-bot for H. Peter Anvin" <hpa@linux.intel.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
stable@vger.kernel.org, arnd@arndb.de, tglx@linutronix.de,
hpa@linux.intel.com, hjl.tools@gmail.com
Subject: [tip:x86/urgent] asm-generic: Use __BITS_PER_LONG in statfs.h
Date: Mon, 30 Apr 2012 16:46:59 -0700 [thread overview]
Message-ID: <tip-f5c2347ee20a8d6964d6a6b1ad04f200f8d4dfa7@git.kernel.org> (raw)
In-Reply-To: <1335465916-16965-1-git-send-email-hpa@linux.intel.com>
Commit-ID: f5c2347ee20a8d6964d6a6b1ad04f200f8d4dfa7
Gitweb: http://git.kernel.org/tip/f5c2347ee20a8d6964d6a6b1ad04f200f8d4dfa7
Author: H. Peter Anvin <hpa@linux.intel.com>
AuthorDate: Thu, 26 Apr 2012 11:45:16 -0700
Committer: H. Peter Anvin <hpa@linux.intel.com>
CommitDate: Mon, 30 Apr 2012 12:55:15 -0700
asm-generic: Use __BITS_PER_LONG in statfs.h
<asm-generic/statfs.h> is exported to userspace, so using
BITS_PER_LONG is invalid. We need to use __BITS_PER_LONG instead.
This is kernel bugzilla 43165.
Reported-by: H.J. Lu <hjl.tools@gmail.com>
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Link: http://lkml.kernel.org/r/1335465916-16965-1-git-send-email-hpa@linux.intel.com
Acked-by: Arnd Bergmann <arnd@arndb.de>
Cc: <stable@vger.kernel.org>
---
include/asm-generic/statfs.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/asm-generic/statfs.h b/include/asm-generic/statfs.h
index 0fd28e0..c749af9 100644
--- a/include/asm-generic/statfs.h
+++ b/include/asm-generic/statfs.h
@@ -15,7 +15,7 @@ typedef __kernel_fsid_t fsid_t;
* with a 10' pole.
*/
#ifndef __statfs_word
-#if BITS_PER_LONG == 64
+#if __BITS_PER_LONG == 64
#define __statfs_word long
#else
#define __statfs_word __u32
prev parent reply other threads:[~2012-04-30 23:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 18:45 [PATCH] " H. Peter Anvin
2012-04-30 13:57 ` Arnd Bergmann
2012-04-30 23:46 ` tip-bot for H. Peter Anvin [this message]
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=tip-f5c2347ee20a8d6964d6a6b1ad04f200f8d4dfa7@git.kernel.org \
--to=hpa@linux.intel.com \
--cc=arnd@arndb.de \
--cc=hjl.tools@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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