From: BALATON Zoltan <balaton@eik.bme.hu>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/5] sdl2 text console fixes and cleanups.
Date: Sun, 8 Apr 2018 12:52:18 +0200 (CEST) [thread overview]
Message-ID: <alpine.BSF.2.21.1804081251340.49362@zero.eik.bme.hu> (raw)
In-Reply-To: <20180321135041.15768-1-kraxel@redhat.com>
On Wed, 21 Mar 2018, Gerd Hoffmann wrote:
> Gerd Hoffmann (5):
> ui: add ctrl modifier support to kbd_put_qcode_console()
> sdl2: track kbd modifier state unconditionally
> sdl2: enable ctrl modifier keys for text consoles
> sdl2: drop QEMU_KEY_BACKSPACE special case
> sdl2: drop dead code
>
> include/ui/console.h | 2 +-
> ui/console.c | 15 +++++++++++++--
> ui/gtk.c | 4 ++--
> ui/sdl2-input.c | 46 ++++++++++++++++++++--------------------------
> 4 files changed, 36 insertions(+), 31 deletions(-)
Will this be included in 2.12? I haven't seen it reaching master yet.
Regards,
BALATON Zoltan
next prev parent reply other threads:[~2018-04-08 10:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 13:50 [Qemu-devel] [PATCH 0/5] sdl2 text console fixes and cleanups Gerd Hoffmann
2018-03-21 13:50 ` [Qemu-devel] [PATCH 1/5] ui: add ctrl modifier support to kbd_put_qcode_console() Gerd Hoffmann
2018-03-21 13:50 ` [Qemu-devel] [PATCH 2/5] sdl2: track kbd modifier state unconditionally Gerd Hoffmann
2018-03-21 13:50 ` [Qemu-devel] [PATCH 3/5] sdl2: enable ctrl modifier keys for text consoles Gerd Hoffmann
2018-03-21 13:50 ` [Qemu-devel] [PATCH 4/5] sdl2: drop QEMU_KEY_BACKSPACE special case Gerd Hoffmann
2018-03-21 13:50 ` [Qemu-devel] [PATCH 5/5] sdl2: drop dead code Gerd Hoffmann
2018-04-08 10:52 ` BALATON Zoltan [this message]
2018-04-09 9:43 ` [Qemu-devel] [PATCH 0/5] sdl2 text console fixes and cleanups Gerd Hoffmann
2018-04-09 10:16 ` Mark Cave-Ayland
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=alpine.BSF.2.21.1804081251340.49362@zero.eik.bme.hu \
--to=balaton@eik.bme.hu \
--cc=kraxel@redhat.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).