From: Peter Maydell <peter.maydell@linaro.org>
To: marcin.juszkiewicz@linaro.org
Cc: qemu-devel@nongnu.org, qemu-arm@nongnu.org,
Leif Lindholm <quic_llindhol@quicinc.com>
Subject: Re: [PATCH v3 0/4] hw/arm/sbsa-ref: platform version 0.1
Date: Thu, 25 May 2023 11:08:25 +0100 [thread overview]
Message-ID: <CAFEAcA8VxcdRvrRN2-pztriakGsXoGhaEcyptJ9z-0rPua0HGw@mail.gmail.com> (raw)
In-Reply-To: <20230524113308.834675-1-marcin.juszkiewicz@linaro.org>
On Wed, 24 May 2023 at 12:33, Marcin Juszkiewicz
<marcin.juszkiewicz@linaro.org> wrote:
>
> About year ago support for setting platform version for sbsa-ref was
> added with "0.0" value.
>
> This patchset bumps it to "0.1" as we export basic GIC information via
> DeviceTree to the firmware. TF-A will then take it and provide to EDK2
> via Secure Monitor Call (instead of using hardcoded values).
>
> Basic documentation about platform changes added.
>
> Marcin Juszkiewicz (3):
> hw/arm/sbsa-ref: add GIC node into DT
> docs: sbsa: correct graphics card name
> docs: sbsa: document platform version changes
The cover message subject says there should be 4 patches
in this series, but there are only 3 listed here and
only 3 emails arrived on list. Is there a missing patch?
thanks
-- PMM
next prev parent reply other threads:[~2023-05-25 10:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 11:33 [PATCH v3 0/4] hw/arm/sbsa-ref: platform version 0.1 Marcin Juszkiewicz
2023-05-24 11:33 ` [PATCH v3 1/4] hw/arm/sbsa-ref: add GIC node into DT Marcin Juszkiewicz
2023-05-24 11:33 ` [PATCH v3 2/4] docs: sbsa: correct graphics card name Marcin Juszkiewicz
2023-05-24 11:33 ` [PATCH v3 3/4] docs: sbsa: document platform version changes Marcin Juszkiewicz
2023-05-30 12:36 ` Peter Maydell
2023-05-25 10:08 ` Peter Maydell [this message]
2023-05-26 8:06 ` [PATCH v3 0/4] hw/arm/sbsa-ref: platform version 0.1 Marcin Juszkiewicz
2023-05-30 12:37 ` Peter Maydell
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=CAFEAcA8VxcdRvrRN2-pztriakGsXoGhaEcyptJ9z-0rPua0HGw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=marcin.juszkiewicz@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quic_llindhol@quicinc.com \
/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).