All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Salisbury <mbs@mc.com>
To: "Timothy A. Seufert" <tas@mindspring.com>
Cc: "Albert D. Cahalan" <acahalan@cs.uml.edu>,
	linuxppc-dev@lists.linuxppc.org, dan@mvista.com,
	hobold@Informatik.Uni-Bremen.DE, nicoya@apia.dhs.org
Subject: Re: ppc LE questions (seeking help hand info pointers)
Date: Mon, 24 Sep 2001 13:10:51 -0400	[thread overview]
Message-ID: <3BAF691B.9020207@mc.com> (raw)
In-Reply-To: p05100302b7d16386402f@[10.0.0.42]


Timothy A. Seufert wrote:

> Assuming you've identified all the needed changes for PPC LE with a
> LE board (*), I humbly submit that Mark & co. should get to work
> making a patch if they really want this feature.  The only item which
> might touch very much code is #5 (anybody know how frequently such
> instructions are used?), and a strong argument can be made that those
> instructions should not be used by anybody given their clearly
> deprecated status.  The rest of it is small enough to be maintained
> outside the regular trees, so they will not lose big time if it gets
> refused for integration.


we'll see how it goes and let you know...


--
/*------------------------------------------------**
**   Mark Salisbury | Mercury Computer Systems    **
**   mbs@mc.com     | System OS - Kernel Team     **
**------------------------------------------------*/


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

  parent reply	other threads:[~2001-09-24 17:10 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-21 18:48 ppc LE questions (seeking help hand info pointers) Albert D. Cahalan
2001-09-22  0:22 ` Timothy A. Seufert
2001-09-22 20:06   ` Albert D. Cahalan
2001-09-24 17:10   ` Mark Salisbury [this message]
2001-09-22 14:23 ` Holger Bettag
2001-09-22 20:26   ` Timothy A. Seufert
  -- strict thread matches above, loose matches on Subject: below --
2001-09-21  5:28 Albert D. Cahalan
2001-09-21  6:10 ` Dan Malek
2001-09-21 10:59   ` Ralph Blach
2001-09-20 15:42 Mark Salisbury
2001-09-20 15:58 ` Tom Rini
2001-09-20 16:07   ` Geert Uytterhoeven
2001-09-20 16:12     ` Tom Rini
2001-09-20 17:10       ` Brad Boyer
2001-09-20 18:32         ` Mark Salisbury
2001-09-20 19:29           ` Holger Bettag
2001-09-20 19:35             ` David Edelsohn
2001-09-20 20:19             ` Mark Salisbury
2001-09-21  1:46               ` Timothy A. Seufert
2001-09-21  3:54                 ` Dan Malek
2001-09-21  7:24                   ` Geert Uytterhoeven
2001-09-21  7:47                     ` Dan Malek
2001-09-21  7:50                       ` Geert Uytterhoeven
2001-09-21  8:19                         ` Dan Malek
2001-09-21 17:01                   ` Ralph Blach
2001-09-21 17:35                     ` David Edelsohn
2001-09-21 18:58                     ` David Edelsohn
2001-09-21 20:22                     ` Dan Malek
2001-09-21 20:29                     ` Benjamin Herrenschmidt
2001-09-21 20:42                       ` Benjamin Herrenschmidt
2001-09-21  7:22                 ` Geert Uytterhoeven
2001-09-21 10:38             ` Ralph Blach
2001-09-20 20:01           ` Tony Mantler
2001-09-20 18:28   ` Mark Salisbury
2001-09-20 19:12     ` Tom Rini
2001-09-20 22:22 ` Dan Malek
2001-09-21  5:45 ` Troy Benjegerdes
2001-09-28  6:37 ` Paul Mackerras

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=3BAF691B.9020207@mc.com \
    --to=mbs@mc.com \
    --cc=acahalan@cs.uml.edu \
    --cc=dan@mvista.com \
    --cc=hobold@Informatik.Uni-Bremen.DE \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=nicoya@apia.dhs.org \
    --cc=tas@mindspring.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 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.