All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Arbuckle <programmingkidx@gmail.com>
To: qemu-devel@nongnu.org, peter.maydell@linaro.org,
	eblake@redhat.com, berrange@redhat.com
Cc: John Arbuckle <programmingkidx@gmail.com>
Subject: [Qemu-devel] [PATCH v3 0/2] Add more function keys support
Date: Mon, 31 Jul 2017 15:44:35 -0400	[thread overview]
Message-ID: <20170731194437.4077-1-programmingkidx@gmail.com> (raw)

QEMU can only handle up to function key F15. These patches extend QEMU to F24. 

John Arbuckle (2):
  Add more function keys to QEMU
  Add more function keys to cocoa.m

 qapi-schema.json  | 16 +++++++++++++++-
 ui/cocoa.m        |  5 +++++
 ui/input-keymap.c | 12 ++++++++++++
 3 files changed, 32 insertions(+), 1 deletion(-)

-- 
2.11.0 (Apple Git-81)

             reply	other threads:[~2017-07-31 19:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-31 19:44 John Arbuckle [this message]
2017-07-31 19:44 ` [Qemu-devel] [PATCH v3 1/2] Add more function keys to QEMU John Arbuckle
2017-08-01  8:34   ` Daniel P. Berrange
2017-07-31 19:44 ` [Qemu-devel] [PATCH v3 2/2] Add more function keys to cocoa.m John Arbuckle

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=20170731194437.4077-1-programmingkidx@gmail.com \
    --to=programmingkidx@gmail.com \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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 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.