All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: startergo <startergo@protonmail.com>
Cc: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [PATCH RFC v1 1/1] ui/sdl2: clipboard sharing implementation for SDL
Date: Wed, 30 Jul 2025 15:04:14 +0100	[thread overview]
Message-ID: <aIomXtsLkLhvi-B1@redhat.com> (raw)
In-Reply-To: <xd4WipyMvVQZAziPe9l9-q6i-sF0qVfag4JY5LGlkHZVTq7jT5BCDLIyT02psvU8fgya1Mj72k1za_MiJFjBTS335JiVREvS9ysZllzbPu0=@protonmail.com>

On Wed, Jul 30, 2025 at 12:23:32PM +0000, startergo wrote:
> From: startergo <startergo@protonmail.com>
> Date: Wed, 30 Jul 2025 12:13:25 +0000
> Subject: [PATCH] ui/sdl2: Add clipboard support with async handling
> 
> This patch adds clipboard support to the SDL2 UI backend with proper
> asynchronous clipboard request handling and QEMU clipboard subsystem
> integration.
> 
> Key features:
> - Runtime stability: QEMU starts and runs without crashes
> - Async handling: Proper async clipboard request tracking
> - Error handling: Comprehensive SDL error reporting
> - Memory management: Correct use of g_autofree and proper cleanup
> - QEMU integration: Full integration with QEMU's clipboard subsystem
> 
> The implementation includes:
> - New meson build option 'sdl_clipboard' (enabled by default)
> - Proper clipboard peer registration and notification handling
> - Async request handling to prevent blocking operations
> - Memory-safe string handling with proper null termination
> 
> Signed-off-by: startergo <startergo@protonmail.com>
> Co-authored-by: Kamay Xutax <admin@xutaxkamay.com>
> ---
> include/ui/sdl2.h | 8 ++
> meson.build | 3 +
> meson_options.txt | 2 +
> ui/meson.build | 3 +
> ui/sdl2-clipboard.c | 154 ++++++++++++++++++++++++++++++++++++++++++
> ui/sdl2.c | 9 +++
> 6 files changed, 179 insertions(+)
> create mode 100644 ui/sdl2-clipboard.c

> +static void sdl2_clipboard_clear_pending(void)
> +{
> + if (pending_request) {
> + if (pending_request->info) {
> + qemu_clipboard_info_unref(pending_request->info);
> + }
> + g_free(pending_request);
> + pending_request = NULL;
> + }
> +}

This mail came through as mixed text + html, and the text part has
completely mangled indentation....

There is no way we can accept the patch in this form, and there
isn't much point in reviewing it either as is.

If you can't get your mail client to send plain text mails without
mangling the patches, then the other option is to use 'git-publish'
as described here:

  https://www.qemu.org/docs/master/devel/submitting-a-patch.html#submitting-your-patches


Also, when posting new versions of a patch, please always send them
as a standalone new emails. Don't send them as a reply to old messages,
as that is liable to result in them going unseen by reviewers.

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  parent reply	other threads:[~2025-07-30 15:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28 12:23 [PATCH RFC v1 1/1] ui/sdl2: clipboard sharing implementation for SDL startergo
2025-07-28 21:40 ` startergo
2025-07-29 12:11 ` Marc-André Lureau
2025-07-30  9:34   ` startergo
2025-07-30 10:04     ` Marc-André Lureau
2025-07-30 12:23       ` startergo
2025-07-30 12:27         ` Marc-André Lureau
2025-07-30 12:44           ` startergo
2025-07-30 12:49             ` Marc-André Lureau
2025-07-30 14:04         ` Daniel P. Berrangé [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-08  2:21 [PATCH RFC v1 0/1] " Kamay Xutax
2023-11-08  2:21 ` [PATCH RFC v1 1/1] ui/sdl2: " Kamay Xutax
2023-11-14 11:23   ` Marc-André Lureau
2023-11-14 12:28     ` BALATON Zoltan
2023-11-14 12:36       ` Marc-André Lureau

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=aIomXtsLkLhvi-B1@redhat.com \
    --to=berrange@redhat.com \
    --cc=marcandre.lureau@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=startergo@protonmail.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 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.