From: Peter Maydell <peter.maydell@linaro.org>
To: Alexander Graf <graf@amazon.com>
Cc: Hendrik Borghorst <hborghor@amazon.de>,
qemu-arm <qemu-arm@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH] pl031: Expose RTCICR as proper WC register
Date: Thu, 14 Nov 2019 21:01:18 +0000 [thread overview]
Message-ID: <CAFEAcA8KyiSvW0c2gM3muM9i-CNSt9qjH0rTDZY8yGcKq0J+5g@mail.gmail.com> (raw)
In-Reply-To: <a3b96c16-4d92-87ea-32a4-f36a62cc857e@amazon.com>
On Thu, 14 Nov 2019 at 20:45, Alexander Graf <graf@amazon.com> wrote:
> On 14.11.19 15:42, Peter Maydell wrote:
> > Is that OK?
>
> It's much better. Will you just fix it up inline for me please? :)
Sure :-)
-- PMM
prev parent reply other threads:[~2019-11-14 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 11:52 [PATCH] pl031: Expose RTCICR as proper WC register Alexander Graf
2019-11-08 15:58 ` Peter Maydell
2019-11-12 7:28 ` Alexander Graf
2019-11-12 11:57 ` Peter Maydell
2019-11-14 13:42 ` Peter Maydell
2019-11-14 20:45 ` Alexander Graf
2019-11-14 21:01 ` Peter Maydell [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=CAFEAcA8KyiSvW0c2gM3muM9i-CNSt9qjH0rTDZY8yGcKq0J+5g@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=graf@amazon.com \
--cc=hborghor@amazon.de \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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).