From: Geoff Levand <geoff@infradead.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Alexander Sverdlin <alexander.sverdlin@gmail.com>,
linuxppc-dev@lists.ozlabs.org, Rob Herring <robh@kernel.org>
Subject: [PATCH v1 0/3] PS3 patches
Date: Mon, 02 Jan 2023 19:41:06 +0000 [thread overview]
Message-ID: <cover.1672687924.git.geoff@infradead.org> (raw)
Hi Michael,
Here are three patches. One is a general powerpc fix for a change commited in
v6.2-rc1. I didn't see anything on the mail list related to this. The other
two patches are updates for PS3.
The following changes since commit 88603b6dc419445847923fcb7fe5080067a30f98:
Linux 6.2-rc2 (2023-01-01 13:53:16 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/geoff/ps3-linux.git for-merge-powerpc-1
for you to fetch changes up to 760a803c300cb2d10548633fc13ed37a5703b026:
powerpc/ps3: Refresh ps3_defconfig (2023-01-02 11:24:20 -0800)
----------------------------------------------------------------
Geoff Levand (3):
powerpc: Fix processing of CONFIG_CMDLINE
powerpc/ps3: Change updateboltedpp panic to info
powerpc/ps3: Refresh ps3_defconfig
arch/powerpc/configs/ps3_defconfig | 39 +++++++++++++++++---------------------
arch/powerpc/kernel/prom.c | 2 +-
arch/powerpc/platforms/ps3/htab.c | 2 +-
3 files changed, 19 insertions(+), 24 deletions(-)
--
2.34.1
next reply other threads:[~2023-01-02 19:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 19:41 Geoff Levand [this message]
2023-01-02 19:41 ` [PATCH v1 1/3] powerpc: Fix processing of CONFIG_CMDLINE Geoff Levand
2023-01-03 2:03 ` Rob Herring
2023-01-03 16:44 ` Geoff Levand
2023-01-03 17:06 ` Rob Herring
2023-01-02 19:41 ` [PATCH v1 2/3] powerpc/ps3: Change updateboltedpp panic to info Geoff Levand
2023-01-02 19:41 ` [PATCH v1 3/3] powerpc/ps3: Refresh ps3_defconfig 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.1672687924.git.geoff@infradead.org \
--to=geoff@infradead.org \
--cc=alexander.sverdlin@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=robh@kernel.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).