From: David Miller <davem@davemloft.net> To: sam@ravnborg.org Cc: akpm@linux-foundation.org, sparclinux@vger.kernel.org, mingo@elte.hu, sfr@canb.auug.org.au, linux-kernel@vger.kernel.org, kenchen@google.com, paulus@samba.org, tglx@linutronix.de, hpa@zytor.com, linux-next@vger.kernel.org Subject: Re: [PATCH] sparc64: use unsigned long long for u64 Date: Sat, 27 Dec 2008 20:25:52 -0800 (PST) [thread overview] Message-ID: <20081227.202552.27482357.davem@davemloft.net> (raw) In-Reply-To: <20081227094955.GA1355@uranus.ravnborg.org> From: Sam Ravnborg <sam@ravnborg.org> Date: Sat, 27 Dec 2008 10:49:55 +0100 > I have ordered a used Sun Blade 100(*) that should show up > before new eve. > So when I have it and it is up and running I will redo this > patch set. That will likely take a few weeks though. Another option, of course, is to use 64-bit cross tools on an x86_64 system if you have access to one of those. > (*) Any distribution recommendations? I will only use it for > sparc kernel development so nothing fancy... Debian testing works fine, and that's what I'm typing this on.
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net> To: sam@ravnborg.org Cc: akpm@linux-foundation.org, sparclinux@vger.kernel.org, mingo@elte.hu, sfr@canb.auug.org.au, linux-kernel@vger.kernel.org, kenchen@google.com, paulus@samba.org, tglx@linutronix.de, hpa@zytor.com, linux-next@vger.kernel.org Subject: Re: [PATCH] sparc64: use unsigned long long for u64 Date: Sun, 28 Dec 2008 04:25:52 +0000 [thread overview] Message-ID: <20081227.202552.27482357.davem@davemloft.net> (raw) In-Reply-To: <20081227094955.GA1355@uranus.ravnborg.org> From: Sam Ravnborg <sam@ravnborg.org> Date: Sat, 27 Dec 2008 10:49:55 +0100 > I have ordered a used Sun Blade 100(*) that should show up > before new eve. > So when I have it and it is up and running I will redo this > patch set. That will likely take a few weeks though. Another option, of course, is to use 64-bit cross tools on an x86_64 system if you have access to one of those. > (*) Any distribution recommendations? I will only use it for > sparc kernel development so nothing fancy... Debian testing works fine, and that's what I'm typing this on.
next prev parent reply other threads:[~2008-12-28 4:26 UTC|newest] Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-12-22 4:22 linux-next: sched tree build warning Stephen Rothwell 2008-12-22 6:47 ` Ingo Molnar 2008-12-22 6:49 ` Ken Chen 2008-12-22 7:04 ` Ingo Molnar 2008-12-22 7:19 ` Stephen Rothwell 2008-12-22 8:03 ` [patch] powerpc: change u64/s64 to a long long integer type Ingo Molnar 2008-12-22 22:43 ` Andrew Morton 2008-12-22 23:00 ` Sam Ravnborg 2008-12-22 23:03 ` H. Peter Anvin 2008-12-22 23:13 ` Sam Ravnborg 2008-12-22 23:13 ` Andrew Morton 2008-12-23 13:17 ` [PATCH] sparc64: use unsigned long long for u64 Sam Ravnborg 2008-12-23 13:17 ` Sam Ravnborg 2008-12-23 13:17 ` Sam Ravnborg 2008-12-23 14:42 ` [PATCH] sparc64: fix unsigned long long warnings in drivers Sam Ravnborg 2008-12-23 14:42 ` Sam Ravnborg 2008-12-23 17:05 ` [PATCH] sparc64: use unsigned long long for u64 Ken Chen 2008-12-23 17:05 ` Ken Chen 2008-12-23 17:26 ` Sam Ravnborg 2008-12-23 17:26 ` Sam Ravnborg 2008-12-23 17:29 ` Ken Chen 2008-12-23 17:29 ` Ken Chen 2008-12-23 17:34 ` Sam Ravnborg 2008-12-23 17:34 ` Sam Ravnborg 2008-12-27 8:54 ` David Miller 2008-12-27 8:54 ` David Miller 2008-12-27 8:54 ` David Miller 2008-12-27 9:24 ` Sam Ravnborg 2008-12-27 9:24 ` Sam Ravnborg 2008-12-27 9:37 ` David Miller 2008-12-27 9:37 ` David Miller 2008-12-27 9:49 ` Sam Ravnborg 2008-12-27 9:49 ` Sam Ravnborg 2008-12-28 4:25 ` David Miller [this message] 2008-12-28 4:25 ` David Miller 2008-12-28 12:32 ` Sam Ravnborg 2008-12-28 12:32 ` Sam Ravnborg 2008-12-31 4:40 ` [patch] powerpc: change u64/s64 to a long long integer type Stephen Rothwell 2008-12-31 7:52 ` Ingo Molnar 2008-12-22 8:14 ` linux-next: sched tree build warning Paul Mackerras 2008-12-22 8:18 ` Ingo Molnar 2008-12-22 9:44 ` Paul Mackerras 2008-12-22 10:53 ` Ingo Molnar 2008-12-22 12:03 ` Paul Mackerras
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=20081227.202552.27482357.davem@davemloft.net \ --to=davem@davemloft.net \ --cc=akpm@linux-foundation.org \ --cc=hpa@zytor.com \ --cc=kenchen@google.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-next@vger.kernel.org \ --cc=mingo@elte.hu \ --cc=paulus@samba.org \ --cc=sam@ravnborg.org \ --cc=sfr@canb.auug.org.au \ --cc=sparclinux@vger.kernel.org \ --cc=tglx@linutronix.de \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.