All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Philippe Mathieu-Daudé" <philippe.mathieu.daude@gmail.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
	"Emanuele Giuseppe Esposito" <eesposit@redhat.com>,
	qemu-devel@nongnu.org, "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Akihiko Odaki" <akihiko.odaki@gmail.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH-for-7.0 v2] qemu/main-loop: Disable block backend global state assertion on Cocoa
Date: Fri, 25 Mar 2022 10:03:21 +0000	[thread overview]
Message-ID: <CAFEAcA-t0YUmggDSKNG1ArRcSKta9siQz700C3zG5JzY0wkDjg@mail.gmail.com> (raw)
In-Reply-To: <7ae621b5-7451-4a70-d109-f1adbcdaac68@gmail.com>

On Tue, 22 Mar 2022 at 09:35, Philippe Mathieu-Daudé
<philippe.mathieu.daude@gmail.com> wrote:
>
> What is preferred between #2 and #3? I don't have enough knowledge to
> take the decision, which is why I suggested the chicken-hearted "disable
> assert" option #1.

I don't have a strong opinion, but I do strongly think we need
to get a fix of some kind into the tree before rc2, and we
are rapidly running out of time for that. Pick something,
and send patches/pullreq as appropriate, please.

thanks
-- PMM


      parent reply	other threads:[~2022-03-25 10:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22  7:54 [PATCH-for-7.0 v2] qemu/main-loop: Disable block backend global state assertion on Cocoa Philippe Mathieu-Daudé
2022-03-22  8:23 ` Akihiko Odaki
2022-03-22  8:32 ` Paolo Bonzini
2022-03-22  9:20   ` Philippe Mathieu-Daudé
2022-03-22  9:24     ` Peter Maydell
2022-03-22  9:35   ` Philippe Mathieu-Daudé
2022-03-22 10:56     ` Akihiko Odaki
2022-03-25 10:03     ` Peter Maydell [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=CAFEAcA-t0YUmggDSKNG1ArRcSKta9siQz700C3zG5JzY0wkDjg@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=akihiko.odaki@gmail.com \
    --cc=eesposit@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philippe.mathieu.daude@gmail.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 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.