linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Cort Dougan <cort@fsmlabs.com>
To: Benjamin Herrenschmidt <bh40@calva.net>
Cc: linuxppc-dev@lists.linuxppc.org, paulus@linuxcare.com
Subject: Re: bootloader & head.S weirdness (patch)
Date: Mon, 22 Nov 1999 14:40:54 -0700	[thread overview]
Message-ID: <19991122144054.C12973@hq.fsmlabs.com> (raw)
In-Reply-To: <19991122124702.006073@mailhost.mipsys.com>; from Benjamin Herrenschmidt on Mon, Nov 22, 1999 at 12:47:02PM +0100


I'll check this patch with the latest 2.2 to see how it goes.  Would using
the bootinfo structure we talked about a few weeks ago help?  I'd like to
unify things a bit with it but I'm not sure how many problems it would
solve and how many it could cause.

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

  parent reply	other threads:[~1999-11-22 21:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <19991122120429.031138>
1999-11-22 11:47 ` bootloader & head.S weirdness (patch) Benjamin Herrenschmidt
1999-11-22 17:07   ` Benjamin Herrenschmidt
1999-11-22 22:06     ` Cort Dougan
1999-11-23 10:44       ` Benjamin Herrenschmidt
1999-11-23 12:35       ` Benjamin Herrenschmidt
1999-11-22 21:40   ` Cort Dougan [this message]
1999-11-23 10:40     ` Benjamin Herrenschmidt
1999-11-23 17:48       ` Cort Dougan
1999-11-23 18:34         ` Geert Uytterhoeven
1999-11-23 19:16           ` Cort Dougan
1999-11-23 19:35             ` Benjamin Herrenschmidt
1999-11-23 20:16             ` Geert Uytterhoeven
1999-11-23 20:21               ` Cort Dougan
1999-11-24  7:32                 ` Geert Uytterhoeven
     [not found] <19991123133536.013861>
1999-11-23 17:07 ` Benjamin Herrenschmidt
1999-11-23 17:52   ` Cort Dougan
1999-11-23 18:08     ` Benjamin Herrenschmidt

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=19991122144054.C12973@hq.fsmlabs.com \
    --to=cort@fsmlabs.com \
    --cc=bh40@calva.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paulus@linuxcare.com \
    /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).