From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6-git: BITS_PER_LONG
Date: Mon, 9 Jan 2006 18:32:04 +0000 [thread overview]
Message-ID: <20060109183204.GB19131@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.62.0601090956340.2202@schroedinger.engr.sgi.com>
On Mon, Jan 09, 2006 at 09:57:29AM -0800, Christoph Lameter wrote:
> On Sat, 7 Jan 2006, Russell King wrote:
> > With the latest git, I'm seeing a number of:
> >
> > include/asm-generic/atomic.h:20:5: warning: "BITS_PER_LONG" is not defined
> >
> > What's intended here? Should asm-generic/atomic.h include asm/types.h?
>
> asm/types.h should be included by asm/atomic.h.
Disagree - nothing in asm/atomic.h needs asm/types.h. If
asm-generic/atomic.h has this requirement, it should be the one
including asm/types.h (or should it be linux/types.h ?)
> Which arch is this?
ARM.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
prev parent reply other threads:[~2006-01-09 18:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 14:49 Russell King
2006-01-09 17:57 ` Christoph Lameter
2006-01-09 18:32 ` Russell King [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=20060109183204.GB19131@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=clameter@engr.sgi.com \
--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