From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ui/sdl_keysym: Remove obsolete SDL1.2 related code
Date: Mon, 4 Feb 2019 12:06:00 +0100 [thread overview]
Message-ID: <e9068f3c-d4a6-b3a7-d34a-c036e9be86e4@redhat.com> (raw)
In-Reply-To: <20190204102213.GF1905@redhat.com>
On 2019-02-04 11:22, Daniel P. Berrangé wrote:
> On Mon, Feb 04, 2019 at 09:14:05AM +0100, Thomas Huth wrote:
>> Support for SDL1.2 has been removed recently in commit:
>>
>> 0015ca5cbabe0b31d31610ddfaafd90a9e5911a4
>> ("ui: remove support for SDL1.2 in favour of SDL2")
>>
>> So we can drop the SDL1.2-specific code in sdl_keysym.h now, too.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>> ui/sdl_keysym.h | 73 ---------------------------------------------------------
>> 1 file changed, 73 deletions(-)
>>
>> diff --git a/ui/sdl_keysym.h b/ui/sdl_keysym.h
>> index 599d9fc..6994180 100644
>> --- a/ui/sdl_keysym.h
>> +++ b/ui/sdl_keysym.h
>> @@ -200,79 +200,6 @@ static const name2keysym_t name2keysym[]={
>> { "yacute", 0x0fd},
>> { "thorn", 0x0fe},
>> { "ydiaeresis", 0x0ff},
>> -#if SDL_MAJOR_VERSION == 1
>
> Don't why this was ever here, because this file is never used by SDL2.
> SDL1 passed window system native scan codes, while SDL2 always passes
> USB HID scancodes.
>
> IOW, you can delete this whole file.
Right, seems like this file is not needed anymore. I'll send a v2...
Thanks,
Thomas
prev parent reply other threads:[~2019-02-04 11:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 8:14 [Qemu-devel] [PATCH] ui/sdl_keysym: Remove obsolete SDL1.2 related code Thomas Huth
2019-02-04 8:44 ` no-reply
2019-02-04 10:22 ` Daniel P. Berrangé
2019-02-04 11:06 ` Thomas Huth [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=e9068f3c-d4a6-b3a7-d34a-c036e9be86e4@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).