qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] How to make changes to qapi-types.h
Date: Tue, 1 Mar 2016 09:59:25 +0800	[thread overview]
Message-ID: <20160301015925.GF15213@ad.usersys.redhat.com> (raw)
In-Reply-To: <C47E1CE0-6E90-472F-B2DA-BD618718CC69@gmail.com>

On Mon, 02/29 20:26, Programmingkid wrote:
> I need to add a variable to the QKeyCode enum in the file qapi-types.h. This
> file is auto-generated so using traditional means to create a patch is not
> possible. Would anyone know how I can add to this file?

The file to look at is qapi-schema.json. The generator is also documented in
docs/qapi-code-gen.txt.

Fam

  reply	other threads:[~2016-03-01  1:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-01  1:26 [Qemu-devel] How to make changes to qapi-types.h Programmingkid
2016-03-01  1:59 ` Fam Zheng [this message]
2016-03-01  2:38   ` Programmingkid
2016-03-01  2:51     ` Fam Zheng
2016-03-01 22:13       ` Programmingkid

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=20160301015925.GF15213@ad.usersys.redhat.com \
    --to=famz@redhat.com \
    --cc=programmingkidx@gmail.com \
    --cc=qemu-devel@nongnu.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).