From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: macro@linux-mips.org, linux-mips@linux-mips.org
Subject: Re: [PATCH] Workaround for a sparse warning in include/asm-mips/io.h
Date: Thu, 12 Jul 2007 14:19:21 +0100 [thread overview]
Message-ID: <20070712131921.GE11019@linux-mips.org> (raw)
In-Reply-To: <20070711.235420.18311683.anemo@mba.ocn.ne.jp>
On Wed, Jul 11, 2007 at 11:54:20PM +0900, Atsushi Nemoto wrote:
> Yes, adding 'L' to KSEG1 is another way to silence the warnings. But
> I just thought it was a bit intrusive. And I'm not sure all code are
> OK if KSEG1 is 'signed' ...
The MIPS architecture's idea of the 32 and 64-bit address space is that
32-bit addresses can be sign-extended to 64-bit addresses. This if of
course conflicting with the general Linux idea that virtual addresses are
represented as an unsigned long.
Ralf
next prev parent reply other threads:[~2007-07-12 13:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 14:12 [PATCH] Workaround for a sparse warning in include/asm-mips/io.h Atsushi Nemoto
2007-07-11 14:28 ` Maciej W. Rozycki
2007-07-11 14:54 ` Atsushi Nemoto
2007-07-12 13:19 ` Ralf Baechle [this message]
2007-07-12 13:41 ` Ralf Baechle
2007-07-12 13:41 ` Ralf Baechle
2007-07-12 13:41 ` Ralf Baechle
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=20070712131921.GE11019@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.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