From: Igor Mammedov <imammedo@redhat.com>
To: Dou Liyang <douly.fnst@cn.fujitsu.com>
Cc: Thomas Huth <thuth@redhat.com>,
Takao Indoh <indou.takao@jp.fujitsu.com>,
Eduardo Habkost <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
David Hildenbrand <david@redhat.com>,
qemu-devel@nongnu.org, f4bug@amsat.org,
Paolo Bonzini <pbonzini@redhat.com>,
Alistair Francis <alistair23@gmail.com>,
Marcel Apfelbaum <marcel@redhat.com>,
Izumi Taku <izumi.taku@jp.fujitsu.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v6] NUMA: Enable adding NUMA node implicitly
Date: Wed, 15 Nov 2017 11:32:06 +0100 [thread overview]
Message-ID: <20171115113206.6c782c71@nial.brq.redhat.com> (raw)
In-Reply-To: <e718178a-e42d-ce5c-0037-d27c08a3990e@cn.fujitsu.com>
On Wed, 15 Nov 2017 09:29:22 +0800
Dou Liyang <douly.fnst@cn.fujitsu.com> wrote:
> Hi Igor,
>
> [...]
> >> + parse_numa_node(ms, &node, NULL);
> > I get build break here:
> >
> > numa.c:451:13: error: too few arguments to function ‘parse_numa_node’
> > parse_numa_node(ms, &node, NULL);
> >
>
> In upstream tree, your commit
>
> cc001888b780 ("numa: fixup parsed NumaNodeOptions earlier")
>
> removed a argument from parse_numa_node() recently. this definition
> of function becomes
>
> static void parse_numa_node(MachineState *ms, NumaNodeOptions *node,
> Error **errp)
>
> this patch is based on the upstream tree, parse_numa_node() should have
> three arguments.
>
> I am not sure why you got this building failure log, can you tell me
> which branch did you test?
it looks like I've failed to update master branch and applied it to old master,
so after refetching and applying it again build and tests passes.
(Sorry for noise :/)
>
> Thanks,
> dou
>
>
>
next prev parent reply other threads:[~2017-11-15 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 2:34 [Qemu-devel] [PATCH v6] NUMA: Enable adding NUMA node implicitly Dou Liyang
2017-11-14 15:30 ` Igor Mammedov
2017-11-15 1:29 ` Dou Liyang
2017-11-15 10:32 ` Igor Mammedov [this message]
2017-11-15 10:35 ` Igor Mammedov
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=20171115113206.6c782c71@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=alistair23@gmail.com \
--cc=david@redhat.com \
--cc=douly.fnst@cn.fujitsu.com \
--cc=ehabkost@redhat.com \
--cc=f4bug@amsat.org \
--cc=indou.takao@jp.fujitsu.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--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).