From: Milton Miller <miltonm@bga.com>
To: Arnd Bergmann <arnd@arndb.de>,
Geoff Levand <geoffrey.levand@am.sony.com>
Cc: linux-ppc <linuxppc-dev@ozlabs.org>
Subject: submitted patches
Date: Thu, 8 Jan 2009 07:07:22 -0600 [thread overview]
Message-ID: <2f26be4be72081b3c5b33101b439c368@bga.com> (raw)
I request the following patches in patchwork be considered for 2.6.29:
http://patchwork.ozlabs.org/patch/3778/
powerpc ps3: use smp_request_message_ipi
http://patchwork.ozlabs.org/patch/3780/
powerpc cell: use smp_request_message_ipi
I think they were marked changes requested becase the prereq had
requested changes. Now the fixed version has merged. They still
apply cleanly. I have no hardware to test them.
http://patchwork.ozlabs.org/patch/16340/
powerpc: check crash_base for relocatable kernel
I think this simple version should be merged and sent to stable for 28.
While Michael would like something more intellegent, I think the
simple patch should go to stable and the code can be refined in the
future.
http://patchwork.ozlabs.org/patch/16606/
powerpc: use common cpu_die
This one will change a build error into a possible runtime fault. If
such a fault can be avoided by simply using the existing generic
methods then I think it should be merged. Otherwise, it may be
preferrable to change the config, althoguh its not obvious which
options need to be changed to avpodthe error whereas , and any fault
would require a suspend or hibernation attempt.
Except for the one deferred patch (whcih needs changes) my remaining
patches are new and I think have descriptions os to their impact.
Thanks,
milton
next reply other threads:[~2009-01-08 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 13:07 Milton Miller [this message]
2009-01-12 23:01 ` submitted patches Geoff Levand
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=2f26be4be72081b3c5b33101b439c368@bga.com \
--to=miltonm@bga.com \
--cc=arnd@arndb.de \
--cc=geoffrey.levand@am.sony.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).