From: Leon Alrae <leon.alrae@imgtec.com>
To: Peter Maydell <peter.maydell@linaro.org>, Liviu Ionescu <ilg@livius.net>
Cc: Christopher Covington <christopher.covington@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Matthew Fortune <matthew.fortune@imgtec.com>
Subject: Re: [Qemu-devel] [PATCH v4 2/2] semihosting: add --semihosting-config arg sub-argument
Date: Tue, 16 Jun 2015 15:20:18 +0100 [thread overview]
Message-ID: <558030A2.1070005@imgtec.com> (raw)
In-Reply-To: <CAFEAcA9tcj2=Uoa0wz2LOpaobgees_cFO=SCq6DFsKv51LMSKA@mail.gmail.com>
On 16/06/2015 15:03, Peter Maydell wrote:
> On 16 June 2015 at 13:32, Liviu Ionescu <ilg@livius.net> wrote:
>> would it be possible to have all the semihosting patches ready for 2.4?
>
> Yes, I agree that would be good. Is it just this 2 patch
> series, or are there others too?
Just to confirm -- the only thing required before applying this 2 patch series
is testing in ARM context by you, right?
Remaining semihosting patches I've got are MIPS specific, but they can go via
target-mips tree separately.
Leon
next prev parent reply other threads:[~2015-06-16 14:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 16:03 [Qemu-devel] [PATCH v4 0/2] semihosting: clean up and add --semihosting-config arg Leon Alrae
2015-05-26 16:03 ` [Qemu-devel] [PATCH v4 1/2] semihosting: create SemihostingConfig structure and semihost.h Leon Alrae
2015-05-26 16:03 ` [Qemu-devel] [PATCH v4 2/2] semihosting: add --semihosting-config arg sub-argument Leon Alrae
2015-06-05 15:23 ` Peter Maydell
2015-06-05 20:09 ` Leon Alrae
2015-06-05 21:11 ` Liviu Ionescu
2015-06-05 22:54 ` Peter Maydell
2015-06-06 8:50 ` Liviu Ionescu
2015-06-16 12:32 ` Liviu Ionescu
2015-06-16 14:03 ` Peter Maydell
2015-06-16 14:20 ` Leon Alrae [this message]
2015-06-18 12:29 ` Peter Maydell
2015-06-03 12:30 ` [Qemu-devel] [PATCH v4 0/2] semihosting: clean up and add --semihosting-config arg Leon Alrae
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=558030A2.1070005@imgtec.com \
--to=leon.alrae@imgtec.com \
--cc=christopher.covington@linaro.org \
--cc=ilg@livius.net \
--cc=matthew.fortune@imgtec.com \
--cc=peter.maydell@linaro.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 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.