From: Mark Salter <msalter@redhat.com>
To: Graeme Gregory <graeme.gregory@linaro.org>, linux-acpi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, rjw@rjwysocki.net, lenb@kernel.org,
lho@apm.com, gregkh@linuxfoundation.org, jcm@redhat.com
Subject: Re: [PATCH 0/2] Updated SPCR quirks for Moonshot/Mustang
Date: Sat, 05 Aug 2017 22:26:28 -0400 [thread overview]
Message-ID: <1501986388.14060.44.camel@redhat.com> (raw)
In-Reply-To: <20170804214944.3910-1-graeme.gregory@linaro.org>
On Fri, 2017-08-04 at 22:49 +0100, Graeme Gregory wrote:
> A couple of patches to build on the SPCR quirks support already upstreamed.
>
> 1 - Moonshot m400 cartridge has the same soc but ACPI tables have different
> HPe specific headers so extend quirk to understand those too.
>
> 2 - Relevant vendors do not seem to be working on DBG2/SPCR update for
> situation where the clock is unknown. We want these machines to boot with
> console initialised from SPCR before I die of old age so use the previous
> quirk handling to also handle the clock problem as well.
>
> Thanks
>
> Graeme
For the series:
Tested-by: Mark Salter <msalter@redhat.com>
Reviewed-by: Mark Salter <msalter@redhat.com>
prev parent reply other threads:[~2017-08-06 2:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 21:49 [PATCH 0/2] Updated SPCR quirks for Moonshot/Mustang Graeme Gregory
2017-08-04 21:49 ` [PATCH 1/2] ACPI: SPCR: extend XGENE 8250 workaround to m400 Graeme Gregory
2017-08-04 21:49 ` [PATCH 2/2] ACPI: SPCR: work around clock issue on xgene UART Graeme Gregory
2017-08-04 22:51 ` [PATCH 0/2] Updated SPCR quirks for Moonshot/Mustang Rafael J. Wysocki
2017-08-05 7:25 ` Graeme Gregory
2017-08-05 12:29 ` Rafael J. Wysocki
2017-08-05 12:32 ` Rafael J. Wysocki
2017-08-10 23:09 ` Rafael J. Wysocki
2017-08-06 2:26 ` Mark Salter [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=1501986388.14060.44.camel@redhat.com \
--to=msalter@redhat.com \
--cc=graeme.gregory@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jcm@redhat.com \
--cc=lenb@kernel.org \
--cc=lho@apm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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.