Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Harald Koerfgen <hkoerfg@web.de>,
	linux-mips@fnet.fr, linux-mips@oss.sgi.com
Subject: Re: [patch] linux 2.4.5: Export mips_machtype
Date: Mon, 13 Aug 2001 17:53:57 +0200	[thread overview]
Message-ID: <20010813175357.E2228@bacchus.dhis.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1010813152457.18279F-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Mon, Aug 13, 2001 at 03:26:23PM +0200

On Mon, Aug 13, 2001 at 03:26:23PM +0200, Maciej W. Rozycki wrote:

>  The following patch exports mips_machtype to modules.  Please apply.

Ok - but I'd like to burry the whole mips_machtype mechanism in 2.5.  To
messy and requires a central authority to allocate machine types.  What
do you think?

  Ralf

  reply	other threads:[~2001-08-13 15:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-13 13:26 [patch] linux 2.4.5: Export mips_machtype Maciej W. Rozycki
2001-08-13 15:53 ` Ralf Baechle [this message]
2001-08-13 16:36   ` Maciej W. Rozycki
2001-08-13 18:27     ` Gleb O. Raiko
2001-08-14 17:43       ` Maciej W. Rozycki
2001-08-15 17:44         ` Keith M Wesolowski
2001-08-15 18:04           ` Ilya Volynets
2001-08-16  8:04         ` Soft-Float emulation with gcc - pr3900 Zoon
2001-08-23 11:38         ` [patch] linux 2.4.5: Export mips_machtype Gleb O. Raiko
2001-08-23 15:59           ` Maciej W. Rozycki
2001-08-23 17:05             ` Jun Sun
2001-08-23 17:31               ` Maciej W. Rozycki
2001-08-24  9:37                 ` Gleb O. Raiko
2001-08-24 15:57                   ` Maciej W. Rozycki
2001-08-24 17:23                   ` Jun Sun
2001-08-24  9:42             ` Gleb O. Raiko
2001-08-24 16:10               ` Maciej W. Rozycki
2001-08-13 19:39   ` Harald Koerfgen

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=20010813175357.E2228@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=hkoerfg@web.de \
    --cc=linux-mips@fnet.fr \
    --cc=linux-mips@oss.sgi.com \
    --cc=macro@ds2.pg.gda.pl \
    /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