From: Igor Mammedov <imammedo@redhat.com>
To: gengdongjiu <gengdongjiu@huawei.com>
Cc: fam@euphon.net, peter.maydell@linaro.org,
xiaoguangrong.eric@gmail.com, kvm@vger.kernel.org,
mst@redhat.com, mtosatti@redhat.com, qemu-devel@nongnu.org,
ehabkost@redhat.com, linuxarm@huawei.com,
shannon.zhaosl@gmail.com, zhengxiang9@huawei.com,
qemu-arm@nongnu.org, Jonathan.Cameron@huawei.com,
pbonzini@redhat.com, "Philippe Mathieu-Daudé" <philmd@redhat.com>,
rth@twiddle.net
Subject: Re: [PATCH v26 01/10] acpi: nvdimm: change NVDIMM_UUID_LE to a common macro
Date: Mon, 11 May 2020 21:41:57 +0200 [thread overview]
Message-ID: <20200511214157.6a64526a@redhat.com> (raw)
In-Reply-To: <777c44a0-b977-a8fe-a3c6-5b217e9093af@huawei.com>
On Mon, 11 May 2020 22:05:28 +0800
gengdongjiu <gengdongjiu@huawei.com> wrote:
> >> + (node3), (node4), (node5) }
> >> +
> >> #define UUID_FMT "%02hhx%02hhx%02hhx%02hhx-" \
> >> "%02hhx%02hhx-%02hhx%02hhx-" \
> >> "%02hhx%02hhx-" \
> >> diff --git a/slirp b/slirp
> >> index 2faae0f..55ab21c 160000
> >> --- a/slirp
> >> +++ b/slirp
> >> @@ -1 +1 @@
> >> -Subproject commit 2faae0f778f818fadc873308f983289df697eb93
> >> +Subproject commit 55ab21c9a36852915b81f1b41ebaf3b6509dd8ba
> >
> > The SLiRP submodule change is certainly unrelated.
>
> Thanks Philippe's review and comments. I submitted another patchset "[PATCH RESEND v26 00/10] Add ARMv8 RAS virtualization support in QEMU" to fix it, please review that patchset.
for future, adding RESEND doesn't make sence here. If you change patches then just bump version.
>
> >
> >
> > .
> >
>
next prev parent reply other threads:[~2020-05-11 19:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 13:41 [PATCH v26 00/10] Add ARMv8 RAS virtualization support in QEMU Dongjiu Geng
2020-05-07 13:41 ` [PATCH v26 01/10] acpi: nvdimm: change NVDIMM_UUID_LE to a common macro Dongjiu Geng
2020-05-11 12:29 ` Philippe Mathieu-Daudé
2020-05-11 14:03 ` gengdongjiu
2020-05-11 14:05 ` gengdongjiu
2020-05-11 19:41 ` Igor Mammedov [this message]
2020-05-12 3:06 ` gengdongjiu
2020-05-07 13:41 ` [PATCH v26 02/10] hw/arm/virt: Introduce a RAS machine option Dongjiu Geng
2020-05-07 13:41 ` [PATCH v26 03/10] docs: APEI GHES generation and CPER record description Dongjiu Geng
2020-05-07 13:41 ` [PATCH v26 04/10] ACPI: Build related register address fields via hardware error fw_cfg blob Dongjiu Geng
2020-05-07 13:42 ` [PATCH v26 05/10] ACPI: Build Hardware Error Source Table Dongjiu Geng
2020-05-07 13:42 ` [PATCH v26 06/10] ACPI: Record the Generic Error Status Block address Dongjiu Geng
2020-05-07 13:42 ` [PATCH v26 07/10] KVM: Move hwpoison page related functions into kvm-all.c Dongjiu Geng
2020-05-07 13:42 ` [PATCH v26 08/10] ACPI: Record Generic Error Status Block(GESB) table Dongjiu Geng
2020-05-07 13:42 ` [PATCH v26 09/10] target-arm: kvm64: handle SIGBUS signal from kernel or KVM Dongjiu Geng
2020-05-07 13:42 ` [PATCH v26 10/10] MAINTAINERS: Add ACPI/HEST/GHES entries Dongjiu Geng
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=20200511214157.6a64526a@redhat.com \
--to=imammedo@redhat.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=ehabkost@redhat.com \
--cc=fam@euphon.net \
--cc=gengdongjiu@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=shannon.zhaosl@gmail.com \
--cc=xiaoguangrong.eric@gmail.com \
--cc=zhengxiang9@huawei.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).