All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Matthias Urlichs <smurf@smurf.noris.de>
Cc: 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 14:49:04 +0100	[thread overview]
Message-ID: <20040905144904.A30552@infradead.org> (raw)
In-Reply-To: <20040905131948.GE2605@kiste>; from smurf@smurf.noris.de on Sun, Sep 05, 2004 at 03:19:48PM +0200

On Sun, Sep 05, 2004 at 03:19:48PM +0200, Matthias Urlichs wrote:
> Hi,
> 
> Christoph Hellwig:
> > > Hence if no one objects, I'll submit the patch to Andrew and Linus.
> > 
> > the common code changes below are not okay.
> 
> 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.


  reply	other threads:[~2004-09-05 13:49 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 [this message]
2004-09-05 15:45           ` Roman Zippel
2004-09-05 15:48           ` Matthias Urlichs

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=20040905144904.A30552@infradead.org \
    --to=hch@infradead.org \
    --cc=dank@kegel.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=smurf@smurf.noris.de \
    --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.