From: Daniel Phillips <phillips@arcor.de>
To: Jens Axboe <axboe@suse.de>
Cc: Rik van Riel <riel@conectiva.com.br>,
Richard.Zidlicky@stud.informatik.uni-erlangen.de,
zippel@linux-m68k.org, linux-m68k@lists.linux-m68k.org,
linux-kernel@vger.kernel.org
Subject: Re: 2.4 mm trouble [possible lru race]
Date: Tue, 1 Oct 2002 20:14:52 +0200 [thread overview]
Message-ID: <E17wRXo-0005vk-00@starship> (raw)
In-Reply-To: <20021001180442.GI5755@suse.de>
On Tuesday 01 October 2002 20:04, Jens Axboe wrote:
> On Tue, Oct 01 2002, Daniel Phillips wrote:
> > On Tuesday 01 October 2002 19:31, Jens Axboe wrote:
> > > Again, m68k was the target.
> >
> > Sure fine, no good reason to be cryptic about it though.
> >
> > #error "m68k doesn't do SMP yet"
> >
> > So SMP must be off or the compile would abort. Well, the only interesting
>
> There's no CONFIG_SMP in the m68k arch config.in. Anyways, enough
> beating of dead horse :)
The horse isn't dead yet, it's still twitching a little. At this
point we still need to speculate about wny anyone would want an SMP
Dragonball machine ;-)
--
Daniel
next prev parent reply other threads:[~2002-10-01 18:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 14:20 2.4 mm trouble [possible lru race] Richard.Zidlicky
2002-10-01 15:12 ` Daniel Phillips
2002-10-01 15:29 ` Daniel Phillips
2002-10-01 16:56 ` Rik van Riel
2002-10-01 17:10 ` Daniel Phillips
2002-10-01 17:31 ` Jens Axboe
2002-10-01 18:01 ` Daniel Phillips
2002-10-01 18:04 ` Jens Axboe
2002-10-01 18:14 ` Daniel Phillips [this message]
2002-10-01 18:22 ` Rik van Riel
2002-10-02 12:07 ` Geert Uytterhoeven
2002-10-02 9:45 ` Richard Zidlicky
-- strict thread matches above, loose matches on Subject: below --
2002-10-20 14:37 Richard Zidlicky
[not found] <20020925122439.C198@linux-m68k.org>
[not found] ` <Pine.LNX.4.44.0209281634240.338-100000@serv>
[not found] ` <20021001112229.A235@linux-m68k.org>
2002-10-01 10:26 ` Daniel Phillips
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=E17wRXo-0005vk-00@starship \
--to=phillips@arcor.de \
--cc=Richard.Zidlicky@stud.informatik.uni-erlangen.de \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=riel@conectiva.com.br \
--cc=zippel@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).