From: Kevin Paul Herbert <kph@cisco.com>
To: linux-mips@linux-mips.org
Subject: [PATCH][2.6]Fix compiler warnings on long long constants in SB1250 build
Date: 15 Jan 2004 11:08:16 -0800 [thread overview]
Message-ID: <1074193693.24675.22.camel@shakedown> (raw)
The following patch corrects warnings in arch/mips/mm/cerr-sb1.c and
arch/mips/sibyte/sb1250/irq.c for "long long" constants.
Kevin
--
Kevin Paul Herbert <kph@cisco.com>
cisco Systems, Inc.
Index: arch/mips/mm/cerr-sb1.c
===================================================================
RCS file: /home/cvs/linux/arch/mips/mm/cerr-sb1.c,v
retrieving revision 1.11
diff -u -r1.11 cerr-sb1.c
--- arch/mips/mm/cerr-sb1.c 18 Nov 2003 01:17:46 -0000 1.11
+++ arch/mips/mm/cerr-sb1.c 15 Jan 2004 19:05:31 -0000
@@ -251,14 +251,14 @@
/* Masks to select bits for Hamming parity, mask_72_64[i] for bit[i] */
static const uint64_t mask_72_64[8] = {
- 0x0738C808099264FFL,
- 0x38C808099264FF07L,
- 0xC808099264FF0738L,
- 0x08099264FF0738C8L,
- 0x099264FF0738C808L,
- 0x9264FF0738C80809L,
- 0x64FF0738C8080992L,
- 0xFF0738C808099264L
+ 0x0738C808099264FFLL,
+ 0x38C808099264FF07LL,
+ 0xC808099264FF0738LL,
+ 0x08099264FF0738C8LL,
+ 0x099264FF0738C808LL,
+ 0x9264FF0738C80809LL,
+ 0x64FF0738C8080992LL,
+ 0xFF0738C808099264LL
};
/* Calculate the parity on a range of bits */
@@ -330,9 +330,9 @@
((lru >> 4) & 0x3),
((lru >> 6) & 0x3));
}
- va = (taglo & 0xC0000FFFFFFFE000) | addr;
+ va = (taglo & 0xC0000FFFFFFFE000LL) | addr;
if ((taglo & (1 << 31)) && (((taglo >> 62) & 0x3) == 3))
- va |= 0x3FFFF00000000000;
+ va |= 0x3FFFF00000000000LL;
valid = ((taghi >> 29) & 1);
if (valid) {
tlo_tmp = taglo & 0xfff3ff;
@@ -473,7 +473,7 @@
: "r" ((way << 13) | addr));
taglo = ((unsigned long long)taglohi << 32) | taglolo;
- pa = (taglo & 0xFFFFFFE000) | addr;
+ pa = (taglo & 0xFFFFFFE000LL) | addr;
if (way == 0) {
lru = (taghi >> 14) & 0xff;
prom_printf("[Bank %d Set 0x%02x] LRU > %d %d %d %d > MRU\n",
Index: arch/mips/sibyte/sb1250/irq.c
===================================================================
RCS file: /home/cvs/linux/arch/mips/sibyte/sb1250/irq.c,v
retrieving revision 1.26
diff -u -r1.26 irq.c
--- arch/mips/sibyte/sb1250/irq.c 10 Nov 2003 17:51:49 -0000 1.26
+++ arch/mips/sibyte/sb1250/irq.c 15 Jan 2004 19:05:32 -0000
@@ -365,9 +365,9 @@
(K_INT_MBOX_0 << 3)));
/* Clear the mailboxes. The firmware may leave them dirty */
- __raw_writeq(0xffffffffffffffff,
+ __raw_writeq(0xffffffffffffffffLL,
IOADDR(A_IMR_REGISTER(0, R_IMR_MAILBOX_CLR_CPU)));
- __raw_writeq(0xffffffffffffffff,
+ __raw_writeq(0xffffffffffffffffLL,
IOADDR(A_IMR_REGISTER(1, R_IMR_MAILBOX_CLR_CPU)));
/* Mask everything except the mailbox registers for both cpus */
reply other threads:[~2004-01-15 19:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1074193693.24675.22.camel@shakedown \
--to=kph@cisco.com \
--cc=linux-mips@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