From: William Lee Irwin III <wli@holomorphy.com>
To: sparclinux@vger.kernel.org
Subject: Re: SMP support in 2.6.x kernel for sparc32
Date: Wed, 28 Jul 2004 23:53:29 +0000 [thread overview]
Message-ID: <20040728235329.GE2334@holomorphy.com> (raw)
In-Reply-To: <001301c474db$af707860$3c01a8c0@cascade>
On Wed, Jul 28, 2004 at 03:06:03PM -0700, William Lee Irwin III wrote:
>>> I expect that this patch will not qualify as stable, esp. given that
On Wed, Jul 28, 2004 at 03:35:35PM -0700, Keith M Wesolowski wrote:
>> Understatement of the year. Note abuse of prom_printf, #if 0, and
>> randomly commented-out lines. If someone sent me this patch as
>> anything other than a curiosity item or cautionary example, I'd K-line
>> him. YHBW.
>> OTOH, if someone wants to clean it up and get it current, that might
>> be useful. I think joshk may have a slightly improved version he was
>> using for a while. Perhaps he can comment here.
On Wed, Jul 28, 2004 at 03:42:30PM -0700, William Lee Irwin III wrote:
> Thanks for the sterner warning. I've got work to do here, but I'm only
> about 36 hours out from OLS and am still trying to catch up with work
> and the rest of email.
I just rediffed the smp patch by brute force vs. 2.6.8-rc2. I'll spin
it up on 3x hypersparc if it turns out the box is actually functional
and see where it explodes sometime in the next 72 hours.
-- wli
next prev parent reply other threads:[~2004-07-28 23:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 19:47 SMP support in 2.6.x kernel for sparc32 Tom Weustink
2004-07-28 22:06 ` William Lee Irwin III
2004-07-28 22:35 ` Keith M Wesolowski
2004-07-28 22:42 ` William Lee Irwin III
2004-07-28 23:53 ` William Lee Irwin III [this message]
2004-07-29 0:05 ` Ciaran McCreesh
2004-07-29 0:11 ` William Lee Irwin III
2004-07-29 4:42 ` Tom Weustink
2004-07-29 5:48 ` William Lee Irwin III
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=20040728235329.GE2334@holomorphy.com \
--to=wli@holomorphy.com \
--cc=sparclinux@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 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.