From: Olof Johansson <olof@lixom.net>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: linux-kernel@vger.kernel.org, Gene Chen <gene.chen@intel.com>,
Benson Leung <bleung@chromium.org>,
Aaron Durbin <adurbin@chromium.org>,
Filipe Brandenburger <filbranden@chromium.org>,
Ben Zhang <benzh@chromium.org>,
Olof Johansson <olofj@chromium.org>,
Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Subject: Re: [PATCHv2 2/3] platform/chrome: pstore: probe for ramoops buffer using acpi
Date: Sun, 6 Mar 2016 12:04:03 -0800 [thread overview]
Message-ID: <20160306200403.GC20171@localhost> (raw)
In-Reply-To: <1455607516-6142-3-git-send-email-enric.balletbo@collabora.com>
On Tue, Feb 16, 2016 at 08:25:15AM +0100, Enric Balletbo i Serra wrote:
> From: Aaron Durbin <adurbin@chromium.org>
>
> In order to handle the firmware placing the ramoops buffer
> in a different location than the kernel is configured to look
> probe for an ACPI device specified by GOOG9999 acpi id. If
> no device is found or the first memory resource is not defined
> properly fall back to the configured base and length.
>
> Signed-off-by: Aaron Durbin <adurbin@chromium.org>
> Signed-off-by: Ben Zhang <benzh@chromium.org>
> Signed-off-by: Filipe Brandenburger <filbranden@chromium.org>
> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> Reviewed-by: Olof Johansson <olofj@chromium.org>
Applied, thanks.
-Olof
next prev parent reply other threads:[~2016-03-06 22:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 7:25 [PATCHv2 0/3] platform/chrome: upstream changes Enric Balletbo i Serra
2016-02-16 7:25 ` [PATCHv2 1/3] platform/chrome: chromeos_laptop: Add Leon Touch Enric Balletbo i Serra
2016-03-06 20:03 ` Olof Johansson
2016-02-16 7:25 ` [PATCHv2 2/3] platform/chrome: pstore: probe for ramoops buffer using acpi Enric Balletbo i Serra
2016-03-06 20:04 ` Olof Johansson [this message]
2016-02-16 7:25 ` [PATCHv2 3/3] platform/chrome: pstore: Move to larger record size Enric Balletbo i Serra
2016-03-06 20:04 ` Olof Johansson
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=20160306200403.GC20171@localhost \
--to=olof@lixom.net \
--cc=adurbin@chromium.org \
--cc=benzh@chromium.org \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=filbranden@chromium.org \
--cc=gene.chen@intel.com \
--cc=gustavo.padovan@collabora.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=olofj@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.