All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: "Lluís Vilanova" <vilanova@ac.upc.edu>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
	Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] [trivial] qapi: Add missing JSON files in build dependencies
Date: Fri, 05 Feb 2016 08:40:34 +0100	[thread overview]
Message-ID: <87vb63d2q5.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <145461055662.15201.2702170180078718114.stgit@localhost> ("Lluís Vilanova"'s message of "Thu, 4 Feb 2016 19:29:17 +0100")

Lluís Vilanova <vilanova@ac.upc.edu> writes:

Suggest to add: "Forgotten in commit 1dde0f4 (trace.json) and commit
fafa4d5 (rocker.json)."  Could be done on commit.

Since I have a QAPI pull request coming up, I can take it through my
tree.

> Signed-off-by: Lluís Vilanova <vilanova@ac.upc.edu>
> ---
>  Makefile |    3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Makefile b/Makefile
> index d0de2d4..30b1b2d 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -272,7 +272,8 @@ $(SRC_PATH)/qga/qapi-schema.json $(SRC_PATH)/scripts/qapi-commands.py $(qapi-py)
>  qapi-modules = $(SRC_PATH)/qapi-schema.json $(SRC_PATH)/qapi/common.json \
>                 $(SRC_PATH)/qapi/block.json $(SRC_PATH)/qapi/block-core.json \
>                 $(SRC_PATH)/qapi/event.json $(SRC_PATH)/qapi/introspect.json \
> -               $(SRC_PATH)/qapi/crypto.json
> +               $(SRC_PATH)/qapi/crypto.json $(SRC_PATH)/qapi/rocker.json \
> +               $(SRC_PATH)/qapi/trace.json
>  
>  qapi-types.c qapi-types.h :\
>  $(qapi-modules) $(SRC_PATH)/scripts/qapi-types.py $(qapi-py)

Thanks!

      parent reply	other threads:[~2016-02-05  7:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04 18:29 [Qemu-devel] [PATCH] [trivial] qapi: Add missing JSON files in build dependencies Lluís Vilanova
2016-02-04 19:28 ` Eric Blake
2016-02-05  7:40 ` Markus Armbruster [this message]

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=87vb63d2q5.fsf@blackfin.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=vilanova@ac.upc.edu \
    /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.