From: Julia Suvorova <jusual@mail.ru>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
"Jim Mussared" <jim@groklearning.com>,
"Steffen Görtz" <mail@steffen-goertz.de>,
"Thomas Huth" <thuth@redhat.com>, "Joel Stanley" <joel@jms.id.au>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3] tests/microbit-test: Check nRF51 UART functionality
Date: Mon, 5 Nov 2018 16:26:24 +0300 [thread overview]
Message-ID: <e36f4d50-d76e-d7b6-e8dd-f961c4475eba@mail.ru> (raw)
In-Reply-To: <87va5bempd.fsf@linaro.org>
On 05.11.2018 15:24, Alex Bennée wrote:
>
> Julia Suvorova via Qemu-devel <qemu-devel@nongnu.org> writes:
>
>> Some functional tests for:
>> Basic reception/transmittion
>> Suspending
>> INTEN* registers
>>
>> Based-on: <20181031002526.14262-1-contrib@steffen-goertz.de>
>> Signed-off-by: Julia Suvorova <jusual@mail.ru>
>> ---
>> This patch was part of nRF51 UART patchset, but wasn't included in the latest
>> revision. Due to upcoming loader fixes, we need this test instead of
>> boot-serial-test, which doesn't support -device loader.
>
> This didn't apply cleanly to master as the test isn't there yet. But the
> uart patches look partially merged. Can I have a reference for the
> series or tree please?
The patch is based on this patchset (patches 7 & 10):
https://lists.nongnu.org/archive/html/qemu-devel/2018-10/msg06718.html
Uart patchset was fully merged except this patch.
Best regards, Julia Suvorova.
next prev parent reply other threads:[~2018-11-05 13:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 10:45 [Qemu-devel] [PATCH v3] tests/microbit-test: Check nRF51 UART functionality Julia Suvorova
2018-11-05 12:24 ` Alex Bennée
2018-11-05 13:26 ` Julia Suvorova [this message]
2018-11-05 15:29 ` no-reply
2018-11-05 15:32 ` no-reply
2018-11-05 16:16 ` Philippe Mathieu-Daudé
2018-11-05 16:36 ` Julia Suvorova
2018-11-05 17:54 ` Peter Maydell
2018-11-08 10:50 ` Stefan Hajnoczi
2018-11-08 10:45 ` Stefan Hajnoczi
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=e36f4d50-d76e-d7b6-e8dd-f961c4475eba@mail.ru \
--to=jusual@mail.ru \
--cc=alex.bennee@linaro.org \
--cc=jim@groklearning.com \
--cc=joel@jms.id.au \
--cc=mail@steffen-goertz.de \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.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).