From: Chris Wright <chrisw@sous-sol.org>
To: "Elangovan, Anush" <anush@fireeye.com>
Cc: linux-kernel@vger.kernel.org, chrisw@sous-sol.org, gregkh@suse.de
Subject: Re: [PATCH] Define BITS_PER_BYTE to fix compilation error in 2.6.15.5
Date: Thu, 2 Mar 2006 10:20:19 -0800 [thread overview]
Message-ID: <20060302182019.GB3883@sorel.sous-sol.org> (raw)
In-Reply-To: <425BE87409B6BA49954C7D375C69F9ED025071B6@ms09.mse4.exchange.ms>
* Elangovan, Anush (anush@fireeye.com) wrote:
>
> 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
Yes, thanks, similar patch is queued.
-chris
next parent reply other threads:[~2006-03-02 18:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <425BE87409B6BA49954C7D375C69F9ED025071B6@ms09.mse4.exchange.ms>
2006-03-02 18:20 ` Chris Wright [this message]
2006-03-02 8:41 Anush Elangovan
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=20060302182019.GB3883@sorel.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=anush@fireeye.com \
--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®