linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Christopher Friesen" <cfriesen@nortel.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, linuxppc64-dev@ozlabs.org
Subject: Re: Patches for 2.6.15
Date: Fri, 28 Oct 2005 10:00:48 -0600	[thread overview]
Message-ID: <43624B30.20600@nortel.com> (raw)
In-Reply-To: <17250.8725.358204.62510@cargo.ozlabs.ibm.com>

Paul Mackerras wrote:

> If possible, I'd like to get to the point where we can remove
> arch/ppc64 entirely by the end of the 2-week merge window for 2.6.15.

I haven't been following this seriously, so forgive me if this has 
already been asked.

Under the unified architecture, what is the machine type in the "uname" 
outout?

Chris

  reply	other threads:[~2005-10-28 16:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-28 13:05 Patches for 2.6.15 Paul Mackerras
2005-10-28 16:00 ` Christopher Friesen [this message]
2005-10-28 17:54   ` Andreas Schwab
2005-10-28 18:41   ` Kumar Gala
2005-10-29  0:10   ` Paul Mackerras
2005-10-28 17:30 ` Matt Porter
2005-10-28 18:44   ` Kumar Gala
2005-10-28 20:02     ` Andrew Morton
2005-10-29  0:20       ` Paul Mackerras
2005-10-29  0:40         ` Andrew Morton
2005-10-29  5:45           ` Paul Mackerras
2005-10-29  5:59             ` Andrew Morton
2005-11-01  5:53   ` Paul Mackerras
2005-11-01 13:22     ` Matt Porter
2005-10-28 18:49 ` Kumar Gala
2005-10-29  8:07   ` Stephen Rothwell
2005-10-29 12:55     ` galak
2005-11-01  5:57   ` Paul Mackerras
2005-10-28 23:11 ` Arnd Bergmann
2005-10-28 23:16   ` [PATCH] reserve syscall numbers for Cell Arnd Bergmann
2005-10-28 23:21   ` Patches for 2.6.15 Andrew Morton

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=43624B30.20600@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc64-dev@ozlabs.org \
    --cc=paulus@samba.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 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).