From: <peng.hao2@zte.com.cn>
To: richard.henderson@linaro.org
Cc: peter.maydell@linaro.org, qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target/arm : add pvpanic mmio device
Date: Wed, 17 Oct 2018 09:39:00 +0800 (CST) [thread overview]
Message-ID: <201810170939000153425@zte.com.cn> (raw)
In-Reply-To: <7847659e-4514-6f4c-a0d7-7434ed486227@linaro.org>
>On 10/17/18 2:23 AM, Peng Hao wrote:
>> +++ b/hw/misc/pvpanic-mmio.c
>> @@ -0,0 +1,76 @@
>> +#include "qemu/osdep.h"
>
>New file requires file header w/ copyright and license.
I will handle it in new version .Thanks
>r~
next prev parent reply other threads:[~2018-10-17 1:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 9:23 [Qemu-devel] [PATCH] target/arm : add pvpanic mmio device Peng Hao
2018-10-17 1:32 ` Richard Henderson
2018-10-17 1:39 ` peng.hao2 [this message]
2018-10-17 9:53 ` Philippe Mathieu-Daudé
2018-10-18 0:55 ` peng.hao2
2018-10-18 12:49 ` Philippe Mathieu-Daudé
-- strict thread matches above, loose matches on Subject: below --
2018-10-17 9:20 Peng Hao
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=201810170939000153425@zte.com.cn \
--to=peng.hao2@zte.com.cn \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).