All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Eric Blake" <eblake@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	qemu-devel@nongnu.org, "Gerd Hoffmann" <kraxel@redhat.com>
Subject: Re: [RFC PATCH] audio: Make the AudiodevDriver enum conditional
Date: Thu, 08 Jul 2021 16:56:29 +0200	[thread overview]
Message-ID: <87v95kdfc2.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <4c27da0d-ef3c-c1da-0d80-d8496292b85c@redhat.com> (Thomas Huth's message of "Fri, 25 Jun 2021 10:45:44 +0200")

Thomas Huth <thuth@redhat.com> writes:

> On 25/06/2021 10.30, Daniel P. Berrangé wrote:
>> On Thu, Jun 24, 2021 at 08:37:16PM +0200, Thomas Huth wrote:
>>> This way, the upper layers like libvirt could have the possibility
>>> to use QAPI to find out which audio drivers have been enabled during
>>> compile-time of QEMU.
>>>
>>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>>> ---
>>>   Note: Marked as RFC since it's quite a lot of ifdef'ing here...
>>>         not sure whether I really like it...
>> Same as my patch here:
>>    https://lists.gnu.org/archive/html/qemu-devel/2021-03/msg00654.html
>
> Oh, nice, I guess it means that it's not such a bad idea to introduce
> all those #ifdefs here :-)
>
> Anyway, looks like my patch was incomplete anyway (I just hacked it
> together after my corresponding DisplayType patch - see 
> https://lists.gnu.org/archive/html/qemu-devel/2021-06/msg06529.html),
> since it lacks the wiring via a qapi command, so please disregard this
> RFC PATCH. Are you going to respin your series from March, Daniel?

I reviewed Daniel's series back then, and pointed out a few minor
issues, mostly in commit messages.  I hope that wasn't the reason for it
getting stuck :)



  reply	other threads:[~2021-07-08 14:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-24 18:37 [RFC PATCH] audio: Make the AudiodevDriver enum conditional Thomas Huth
2021-06-25  8:30 ` Daniel P. Berrangé
2021-06-25  8:45   ` Thomas Huth
2021-07-08 14:56     ` Markus Armbruster [this message]
2021-07-08 15:17       ` Daniel P. Berrangé

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=87v95kdfc2.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.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.