linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tom Gall <gall@rochcivictheatre.org>
To: Takashi Oe <toe@unlserve.unl.edu>
Cc: Kaoru Fukui <k_fukui@highway.ne.jp>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Success kernel-243pre8-SMP(patch)(Re: spin_lock problem in recent   kernel
Date: Thu, 29 Mar 2001 20:48:21 -0600	[thread overview]
Message-ID: <3AC3F3F5.427CFAB6@rochcivictheatre.org> (raw)
In-Reply-To: Pine.A41.3.96LJ1.1b7.1010329201445.24912C-100000@unlserve.unl.edu


Takashi Oe wrote:
> He is just commenting out those lines.  They are not "#ifdef CONFIG_SMP".

Sigh ... some days it just doesn't pay to get out of bed... I missed the
'n'....

*BONK *

Thanks!

> Takashi Oe

--
Regards,

Tom

--------------------------------------------------------------
Linux Guy             "My heart is human, my blood is boiling,
gall@rochcivictheatre.org    my brain IBM" -- Mr Roboto, Styxx

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-03-30  2:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-28 17:18 spin_lock problem in recent kernel Kaoru Fukui
2001-03-28 19:02 ` Tom Gall
2001-03-29 13:29   ` Kaoru Fukui
     [not found]     ` <3AC33CA7.E5DF4C03@vnet.ibm.com>
2001-03-29 21:20       ` Success kernel-243pre8-SMP(patch)(Re: spin_lock problem in recent k ernel Kaoru Fukui
2001-03-30  2:18         ` Success kernel-243pre8-SMP(patch)(Re: spin_lock problem in recent kernel Tom Gall
2001-03-30  2:16           ` Takashi Oe
2001-03-30  2:48             ` Tom Gall [this message]
2001-03-30  2:36           ` Tony Mantler
2001-03-30  3:07             ` Success kernel-243pre8-SMP(patch)(Re: spin_lock problem inrecent kernel Tom Gall
2001-03-30 12:40               ` Olaf Hering
2001-03-30  9:16         ` Success kernel-243pre8-SMP(patch)(Re: spin_lock problem in recent k ernel Geert Uytterhoeven

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=3AC3F3F5.427CFAB6@rochcivictheatre.org \
    --to=gall@rochcivictheatre.org \
    --cc=k_fukui@highway.ne.jp \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=toe@unlserve.unl.edu \
    /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;
as well as URLs for NNTP newsgroup(s).