From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Andrew Jones" <drjones@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"QEMU Trivial" <qemu-trivial@nongnu.org>,
qemu-arm <qemu-arm@nongnu.org>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-arm] [PATCH] hw/arm/virt: support 4 serial ports
Date: Thu, 26 Oct 2017 18:36:37 +0200 [thread overview]
Message-ID: <CAHmME9qSJSPjANce_cWN6nm=qJsncfczgk7PoPa0xkOHmZjLUA@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA9XoeXDCQCmRBehntWSo0WGRBsaMDmC8QCqgU1K8jAF_A@mail.gmail.com>
On Thu, Oct 26, 2017 at 6:34 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
> Reordering it would break existing users of the trustzone uart,
> whose command lines would stop working.
I thought this was the reason for all of those virt26, virt28,etc
types -- people who want stability code the revision into their
scripts. Everybody else then gets the latest.
next prev parent reply other threads:[~2017-10-26 16:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 12:27 [Qemu-devel] [PATCH] hw/arm/virt: support 4 serial ports Jason A. Donenfeld
2017-10-23 12:35 ` no-reply
2017-10-23 13:11 ` [Qemu-devel] [Qemu-arm] " Peter Maydell
2017-10-23 13:48 ` Philippe Mathieu-Daudé
2017-10-24 17:57 ` Jason A. Donenfeld
2017-10-26 13:34 ` Andrew Jones
2017-10-26 14:13 ` Jason A. Donenfeld
2017-10-26 14:36 ` Peter Maydell
2017-10-26 16:15 ` Jason A. Donenfeld
2017-10-26 16:34 ` Peter Maydell
2017-10-26 16:36 ` Jason A. Donenfeld [this message]
2017-10-26 16:41 ` Peter Maydell
2017-10-26 17:31 ` Jason A. Donenfeld
2017-12-08 11:49 ` Peter Maydell
2017-12-08 18:39 ` Jason A. Donenfeld
2017-12-10 18:15 ` Peter Maydell
2017-10-23 14:14 ` Jason A. Donenfeld
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='CAHmME9qSJSPjANce_cWN6nm=qJsncfczgk7PoPa0xkOHmZjLUA@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=drjones@redhat.com \
--cc=f4bug@amsat.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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 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.