From: Joel Stanley <joel@jms.id.au>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: devicetree <devicetree@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
linux-aspeed <linux-aspeed@lists.ozlabs.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] ARM: dts: Enable ramoops for Rainier and Tacoma
Date: Wed, 21 Oct 2020 04:51:17 +0000 [thread overview]
Message-ID: <CACPK8Xf1=YEApovVOCbE5dkM3uK0Lsx2iXnVK6nK3mx=+q4jpw@mail.gmail.com> (raw)
In-Reply-To: <20201016043513.119841-1-andrew@aj.id.au>
On Fri, 16 Oct 2020 at 04:36, Andrew Jeffery <andrew@aj.id.au> wrote:
>
> Hi,
>
> We're looking to improve our crash data capture for the BMC on some IBM
> platforms. This small series enables ramoops for Rainier and Tacoma.
>
> Please review.
Reviewed-by: Joel Stanley <joel@jms.id.au>
>
> Andrew
>
> Andrew Jeffery (2):
> ARM: dts: rainier: Add reserved memory for ramoops
> ARM: dts: tacoma: Add reserved memory for ramoops
>
> arch/arm/boot/dts/aspeed-bmc-ibm-rainier.dts | 9 +++++++++
> arch/arm/boot/dts/aspeed-bmc-opp-tacoma.dts | 9 +++++++++
> 2 files changed, 18 insertions(+)
>
> --
> 2.25.1
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-10-21 4:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 4:35 [PATCH 0/2] ARM: dts: Enable ramoops for Rainier and Tacoma Andrew Jeffery
2020-10-16 4:35 ` [PATCH 1/2] ARM: dts: rainier: Add reserved memory for ramoops Andrew Jeffery
2020-10-16 4:35 ` [PATCH 2/2] ARM: dts: tacoma: " Andrew Jeffery
2020-10-21 5:05 ` Joel Stanley
2020-10-21 5:42 ` Andrew Jeffery
2020-10-21 4:51 ` Joel Stanley [this message]
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='CACPK8Xf1=YEApovVOCbE5dkM3uK0Lsx2iXnVK6nK3mx=+q4jpw@mail.gmail.com' \
--to=joel@jms.id.au \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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).