From: "Anush Elangovan" <anush.e@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: chrisw@sous-sol.org, gregkh@suse.de
Subject: [PATCH] Define BITS_PER_BYTE to fix compilation error in 2.6.15.5
Date: Thu, 2 Mar 2006 00:41:40 -0800 [thread overview]
Message-ID: <c38b25e50603020041w405c5f93i611dcb7954dfbbef@mail.gmail.com> (raw)
Looks like mm/mempolicy.c requires BITS_PER_BYTE, which is not defined
in 2.6.15.5. Patch below fixes the issue. 2.6.16rc5 seems to have the
#define
Signed-off-by: Anush Elangovan (anush.e@gmail.com)
diff -rup linux-2.6.15.5/include/linux/types.h
linux-2.6.15.5_fix/include/linux/types.h
--- linux-2.6.15.5/include/linux/types.h 2006-03-01
14:37:27.000000000 -0800
+++ linux-2.6.15.5_fix/include/linux/types.h 2006-03-01
23:39:43.000000000 -0800
@@ -8,6 +8,8 @@
(((bits)+BITS_PER_LONG-1)/BITS_PER_LONG)
#define DECLARE_BITMAP(name,bits) \
unsigned long name[BITS_TO_LONGS(bits)]
+
+#define BITS_PER_BYTE 8
#endif
#include <linux/posix_types.h>
next reply other threads:[~2006-03-02 8:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 8:41 Anush Elangovan [this message]
[not found] <425BE87409B6BA49954C7D375C69F9ED025071B6@ms09.mse4.exchange.ms>
2006-03-02 18:20 ` Chris Wright
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=c38b25e50603020041w405c5f93i611dcb7954dfbbef@mail.gmail.com \
--to=anush.e@gmail.com \
--cc=chrisw@sous-sol.org \
--cc=gregkh@suse.de \
--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
all inboxes | Powered by JetHome®