From: Paul Mackerras <paulus@samba.org>
To: Arnd Bergmann <arnd.bergmann@de.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [RFC/PATCH 0/9] More xmon cell patches
Date: Tue, 21 Nov 2006 09:06:33 +1100	[thread overview]
Message-ID: <17762.9961.976166.744875@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <200611162220.02845.arnd.bergmann@de.ibm.com>
Arnd Bergmann writes:
> Paul, are you taking these patches directly, or should I repost them
> to you along with my other stuff for 2.6.20?
Whichever you prefer - if you ack them on the mailing list I'll put
them in powerpc.git, or if you resend them with your signed-off-by
I'll put them in.
Paul.
next prev parent reply	other threads:[~2006-11-20 22:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-16  7:23 [RFC/PATCH 0/9] More xmon cell patches Michael Ellerman
2006-11-16  7:23 ` [RFC/PATCH 1/9] Fix sparse warning in xmon Cell code Michael Ellerman
2006-11-16  7:23 ` [RFC/PATCH 3/9] Add a 'sd' command (spu dump) to xmon to dump spu local store Michael Ellerman
2006-11-16  7:23 ` [RFC/PATCH 2/9] Show state of spus as they're stopped in Cell xmon helper Michael Ellerman
2006-11-16  7:23 ` [RFC/PATCH 4/9] Prepare for spu disassembly in xmon Michael Ellerman
2006-11-16  7:23 ` [RFC/PATCH 5/9] Import spu disassembly code into xmon Michael Ellerman
2006-11-16  7:23 ` [RFC/PATCH 6/9] Add spu disassembly to xmon Michael Ellerman
2006-11-16  7:23 ` [RFC/PATCH 7/9] Make xmon disassembly optional Michael Ellerman
2006-11-16  7:23 ` [RFC/PATCH 8/9] Make 64-bit cpu features defined on 32-bit Michael Ellerman
2006-11-16 10:17   ` Stephen Rothwell
2006-11-16 23:03     ` Michael Ellerman
2006-11-16  7:23 ` [RFC/PATCH 9/9] Import updated version of ppc disassembly code for xmon Michael Ellerman
2006-11-16 21:20 ` [RFC/PATCH 0/9] More xmon cell patches Arnd Bergmann
2006-11-20 22:06   ` Paul Mackerras [this message]
2006-11-21 10:24 ` Arnd Bergmann
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=17762.9961.976166.744875@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=arnd.bergmann@de.ibm.com \
    --cc=linuxppc-dev@ozlabs.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).