From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Peter Lieven" <pl@kamp.de>, "Hanna Reitz" <hreitz@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Ronnie Sahlberg" <ronniesahlberg@gmail.com>,
qemu-block@nongnu.org, libvir-list@redhat.com,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Kevin Wolf" <kwolf@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Eric Blake" <eblake@redhat.com>
Subject: [PULL 0/3] Misc next patches
Date: Tue, 14 Mar 2023 16:25:37 +0000 [thread overview]
Message-ID: <20230314162540.385954-1-berrange@redhat.com> (raw)
The following changes since commit 5cfda4ce79dd455f1726874a555260a70f84b2ec:
Merge tag 'pull-request-2023-03-13' of https://gitlab.com/thuth/qemu into staging (2023-03-13 17:09:33 +0000)
are available in the Git repository at:
https://gitlab.com/berrange/qemu tags/misc-next-pull-request
for you to fetch changes up to c3a2c84ae3c1d5483ec30731321a674797dc5203:
io/channel-tls: plug memory leakage on GSource (2023-03-14 13:41:21 +0000)
----------------------------------------------------------------
Miscellaneous fixes
* Avoid memory leak in TLS GSource usage
* Avoid sending key releases for lang1/lang2 keys in ps2 keyboard
* Add missing key name constants for F13-F24 keys
----------------------------------------------------------------
Matheus Tavares Bernardino (1):
io/channel-tls: plug memory leakage on GSource
Ross Lagerwall (1):
ps2: Don't send key release event for Lang1, Lang2 keys
Willem van de Velde (1):
Add qemu qcode support for keys F13 to F24
hw/input/ps2.c | 6 ++++++
io/channel-tls.c | 1 +
qapi/ui.json | 15 ++++++++++++++-
ui/keycodemapdb | 2 +-
4 files changed, 22 insertions(+), 2 deletions(-)
--
2.39.2
next reply other threads:[~2023-03-14 16:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 16:25 Daniel P. Berrangé [this message]
2023-03-14 16:25 ` [PULL 1/3] Add qemu qcode support for keys F13 to F24 Daniel P. Berrangé
2023-03-14 16:25 ` [PULL 2/3] ps2: Don't send key release event for Lang1, Lang2 keys Daniel P. Berrangé
2023-03-14 16:25 ` [PULL 3/3] io/channel-tls: plug memory leakage on GSource Daniel P. Berrangé
2023-03-16 9:25 ` [PULL 0/3] Misc next patches Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2022-04-26 15:13 Daniel P. Berrangé
2022-04-26 20:12 ` Richard Henderson
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=20230314162540.385954-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=libvir-list@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.com \
/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).