From: Geoff Levand <geoff@infradead.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
Markus Elfring <elfring@users.sourceforge.net>,
Dan Carpenter <dan.carpenter@oracle.com>,
Emmanuel Nicolet <emmanuel.nicolet@gmail.com>
Subject: [PATCH 0/9] PS3 patches for v5.7
Date: Fri, 27 Mar 2020 20:26:23 +0000 [thread overview]
Message-ID: <cover.1585340156.git.geoff@infradead.org> (raw)
Hi Michael,
Here are a few PS3 specific patches. A few remove some reduntant messages,
a few add some minor debugging support, and a few fix some problems during
system boot.
Please consider for v5.7.
-Geoff
The following changes since commit 16fbf79b0f83bc752cee8589279f1ebfe57b3b6e:
Linux 5.6-rc7 (2020-03-22 18:31:56 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/geoff/ps3-linux.git for-merge-ps3
for you to fetch changes up to 1333a8985c4190763c9c0312bcefad8b1ea863c7:
powerpc/ps3: Add udbg_panic (2020-03-27 13:07:31 -0700)
----------------------------------------------------------------
Dan Carpenter (1):
powerpc/ps3: remove an unneeded NULL check
Emmanuel Nicolet (1):
ps3disk: use the default segment boundary
Geoff Levand (4):
powerpc/ps3: Set CONFIG_UEVENT_HELPER=y in ps3_defconfig
powerpc/ps3: Add check for otheros image size
powerpc/ps3: Add lv1_panic
powerpc/ps3: Add udbg_panic
Markus Elfring (3):
powerpc/ps3: Remove duplicate error messages
drivers/ps3: Remove duplicate error messages
net/ps3_gelic_net: Remove duplicate error message
arch/powerpc/boot/ppc_asm.h | 6 ++++++
arch/powerpc/boot/wrapper | 13 +++++++++++--
arch/powerpc/configs/ps3_defconfig | 2 ++
arch/powerpc/include/asm/ppc_asm.h | 6 ++++++
arch/powerpc/platforms/ps3/mm.c | 9 ++++++++-
arch/powerpc/platforms/ps3/os-area.c | 4 +---
drivers/block/ps3disk.c | 1 -
drivers/net/ethernet/toshiba/ps3_gelic_net.c | 2 --
drivers/ps3/ps3-lpm.c | 2 --
drivers/ps3/ps3-vuart.c | 1 -
drivers/ps3/sys-manager-core.c | 2 +-
11 files changed, 35 insertions(+), 13 deletions(-)
--
2.20.1
next reply other threads:[~2020-03-27 20:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 20:26 Geoff Levand [this message]
2020-03-27 20:26 ` [PATCH 5/9] ps3disk: use the default segment boundary Geoff Levand
2020-03-27 20:26 ` [PATCH 9/9] powerpc/ps3: Add udbg_panic Geoff Levand
2020-03-27 20:26 ` [PATCH 6/9] powerpc/ps3: Set CONFIG_UEVENT_HELPER=y in ps3_defconfig Geoff Levand
2020-04-06 13:05 ` Michael Ellerman
2020-03-27 20:26 ` [PATCH 8/9] powerpc/ps3: Add lv1_panic Geoff Levand
2020-03-27 20:26 ` [PATCH 7/9] powerpc/ps3: Add check for otheros image size Geoff Levand
2020-03-29 14:00 ` Geert Uytterhoeven
2020-03-30 3:10 ` Geoff Levand
2020-03-30 3:11 ` [PATCH V2 " Geoff Levand
2020-03-27 20:26 ` [PATCH 4/9] powerpc/ps3: remove an unneeded NULL check Geoff Levand
2020-04-06 13:05 ` Michael Ellerman
2020-03-27 20:26 ` [PATCH 1/9] powerpc/ps3: Remove duplicate error messages Geoff Levand
2020-03-28 17:09 ` Markus Elfring
2020-04-06 13:05 ` Michael Ellerman
2020-03-27 20:26 ` [PATCH 3/9] net/ps3_gelic_net: Remove duplicate error message Geoff Levand
2020-03-27 20:26 ` [PATCH 2/9] drivers/ps3: Remove duplicate error messages 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=cover.1585340156.git.geoff@infradead.org \
--to=geoff@infradead.org \
--cc=dan.carpenter@oracle.com \
--cc=elfring@users.sourceforge.net \
--cc=emmanuel.nicolet@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).