From: "Matthias Urlichs" <smurf@smurf.noris.de>
To: Christoph Hellwig <hch@infradead.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Dan Kegel <dank@kegel.com>, Roman Zippel <zippel@linux-m68k.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux/m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: Getting kernel.org kernel to build for m68k?
Date: Sun, 5 Sep 2004 17:48:11 +0200 [thread overview]
Message-ID: <20040905154811.GF2605@kiste> (raw)
In-Reply-To: <20040905144904.A30552@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 513 bytes --]
Hi,
Christoph Hellwig:
> > Why not?
>
> Because we don't want gazillions of special cases in common code. We
> already added support for allocating the thread_info and task_struct
> as a single object because ia64 needed it, there's no reason to stack
> another hack ontop for m68k.
OK -- I'll investigate changing that. It'll be a few days until I can get
to it however :-/ so if anybody beats me to it, fine.
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | smurf@smurf.noris.de
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-09-05 15:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-01 5:35 Getting kernel.org kernel to build for m68k? Dan Kegel
2004-09-01 8:36 ` Geert Uytterhoeven
2004-09-05 10:41 ` Geert Uytterhoeven
2004-09-05 11:01 ` Matthias Urlichs
2004-09-05 11:03 ` Christoph Hellwig
2004-09-05 13:19 ` Matthias Urlichs
2004-09-05 13:49 ` Christoph Hellwig
2004-09-05 15:45 ` Roman Zippel
2004-09-05 15:48 ` Matthias Urlichs [this message]
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=20040905154811.GF2605@kiste \
--to=smurf@smurf.noris.de \
--cc=dank@kegel.com \
--cc=geert@linux-m68k.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--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 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.