From: Joel Stanley <joel@jms.id.au>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: [PATCH 0/3] Enable pstore for Rainier
Date: Wed, 7 Oct 2020 07:21:16 +0000 [thread overview]
Message-ID: <CACPK8Xd_kbuUVLomHhvkB4KXXuboiNY_HYMpSrJYdjjedjBu_Q@mail.gmail.com> (raw)
In-Reply-To: <20201002063414.275161-1-andrew@aj.id.au>
On Fri, 2 Oct 2020 at 06:35, Andrew Jeffery <andrew@aj.id.au> wrote:
>
> Hello,
>
> This series adds pstore support to the Rainier platform for recovery of oopses
> and panics.
>
> Patch 3/3 is a minor cleanup. Only patch 1/3 is a requirement as 2/3 is handled
> by the config snippet in the bitbake metadata.
I merged 2 and 3. lmk what you want to do with the configuration.
I suggest we enable it for Tacoma too.
>
> Please review!
>
> Andrew
>
> Andrew Jeffery (3):
> ARM: dts: rainier: Add reserved memory for ramoops
> ARM: config: Enable PSTORE in aspeed_g5_defconfig
> ARM: dts: rainier: Don't shout addresses
>
> arch/arm/boot/dts/aspeed-bmc-ibm-rainier.dts | 12 ++++++++++--
> arch/arm/configs/aspeed_g5_defconfig | 4 ++++
> 2 files changed, 14 insertions(+), 2 deletions(-)
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2020-10-07 7:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 6:34 [PATCH 0/3] Enable pstore for Rainier Andrew Jeffery
2020-10-02 6:34 ` [PATCH 1/3] ARM: dts: rainier: Add reserved memory for ramoops Andrew Jeffery
2020-10-06 3:22 ` Joel Stanley
2020-10-16 3:38 ` Andrew Jeffery
2020-10-06 4:25 ` Milton Miller II
2020-10-06 4:29 ` Andrew Jeffery
2020-10-06 4:44 ` Milton Miller II
2020-10-02 6:34 ` [PATCH 2/3] ARM: config: Enable PSTORE in aspeed_g5_defconfig Andrew Jeffery
2020-10-06 3:51 ` Joel Stanley
2020-10-02 6:34 ` [PATCH 3/3] ARM: dts: rainier: Don't shout addresses Andrew Jeffery
2020-10-06 3:51 ` Joel Stanley
2020-10-02 6:38 ` [PATCH 0/3] Enable pstore for Rainier Andrew Jeffery
2020-10-07 7:21 ` Joel Stanley [this message]
2020-10-10 2:50 ` Andrew Jeffery
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=CACPK8Xd_kbuUVLomHhvkB4KXXuboiNY_HYMpSrJYdjjedjBu_Q@mail.gmail.com \
--to=joel@jms.id.au \
--cc=andrew@aj.id.au \
--cc=openbmc@lists.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).