All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Kunz via Qemu-devel <qemu-devel@nongnu.org>
To: marlies.ruck@gmail.com, qemu-devel@nongnu.org,
	riku.voipio@iki.fi,  laurent@vivier.eu
Cc: qemu-trivial@nongnu.org, peter.maydell@linaro.org,
	Shu-Chun Weng <scw@google.com>
Subject: Re: [Qemu-devel] patch to swap SIGRTMIN + 1 and SIGRTMAX - 1
Date: Mon, 19 Aug 2019 14:46:13 -0700	[thread overview]
Message-ID: <CADgy-2vznasvwaUwNSi96Sy=ucPC=-3e=O9irqc5DSpV_uhWUg@mail.gmail.com> (raw)

Hi all,

I have also experienced issues with SIGRTMIN + 1, and am interested in
moving this patch forwards. Anything I can do here to help? Would the
maintainers prefer myself or Marli re-submit the patch?

The Go issue here seems particularly sticky. Even if we update the Go
runtime, users may try and run older binaries built with older versions of
Go for quite some time (months? years?). Would it be better to hide this
behind some kind of build-time flag (`--enable-sigrtmin-plus-one-proxy` or
something), so that some users can opt-in, but older binaries still work as
expected?

Also, here is a link to the original thread this message is in reply to
in-case my mail-client doesn't set up the reply properly:
https://lists.nongnu.org/archive/html/qemu-devel/2019-07/msg01303.html

Thanks,
Josh Kunz

             reply	other threads:[~2019-08-19 22:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19 21:46 Josh Kunz via Qemu-devel [this message]
2019-08-21  9:28 ` [Qemu-devel] patch to swap SIGRTMIN + 1 and SIGRTMAX - 1 Laurent Vivier
2019-08-26 21:10   ` Josh Kunz via Qemu-devel
2019-08-27  8:08     ` Peter Maydell
2019-08-28  8:51     ` Laurent Vivier
2019-08-28 17:31       ` [Qemu-devel] [EXTERNAL]Re: " Aleksandar Markovic
2019-08-31  1:26         ` Josh Kunz via Qemu-devel
2019-10-02 18:06           ` [EXTERNAL]Re: [Qemu-devel] " Josh Kunz
2019-12-07 13:05         ` Aleksandar Markovic
  -- strict thread matches above, loose matches on Subject: below --
2019-06-21 22:58 Marlies Ruck
2019-06-28 23:26 ` Marlies Ruck
2019-06-29 10:53   ` Philippe Mathieu-Daudé
2019-07-01  9:08     ` Peter Maydell
2019-07-01 22:04       ` Marlies Ruck
2019-07-03 21:11         ` Marlies Ruck

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='CADgy-2vznasvwaUwNSi96Sy=ucPC=-3e=O9irqc5DSpV_uhWUg@mail.gmail.com' \
    --to=qemu-devel@nongnu.org \
    --cc=jkz@google.com \
    --cc=laurent@vivier.eu \
    --cc=marlies.ruck@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=riku.voipio@iki.fi \
    --cc=scw@google.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.