qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
To: "Alex Benné e" <alex.bennee@linaro.org>
Cc: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] Add virtio-sound and virtio-sound-pci devices
Date: Fri, 02 Jun 2023 16:36:55 +0300	[thread overview]
Message-ID: <vmope.urd1m26bujz@linaro.org> (raw)
In-Reply-To: <87a5xkde0c.fsf@linaro.org>

On Wed, 31 May 2023 12:36, Alex Bennée <alex.bennee@linaro.org> wrote:
>If it's based of shouldn't we keep the author attribution and their
>original s-o-b?
>

I kept the Copyright in the headers but not the Signed-off-by lines, 
I'll add them in v2.


>What about:
>
>  https://patchew.org/QEMU/20220211221319.193404-1-chouhan.shreyansh2702@gmail.com/
>
>(which is also much more nicely split up).

Comments in that thread were:

> IMHO, all your patches can be merged in only one

and

> Possibly also patches adding
> significant functionality in the future (i.e. one patch with all
> basics and playback support, one patch adding recording
> functionality, ...).

which is why capture was left unimplemented for a future patch:

>> +
>> +    } else {
>> +        /*
>> +         * Unimplemented.
>> +         * stream->voice.in = AUD_open_in(&s->card,
>> +         *                                stream->voice.in,
>> +         *                                "virtio_snd_card",
>> +         *                                stream,
>> +         *                                virtio_snd_input_cb,
>> +         *                                &as);
>> +         */
>
>  qemu_log(LOG_UNIMP, ) - although why not implement it?
>
>> +    }


      reply	other threads:[~2023-06-02 13:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-26 20:48 [PATCH] Add virtio-sound and virtio-sound-pci devices Manos Pitsidianakis
2023-05-31  9:36 ` Alex Bennée
2023-06-02 13:36   ` Manos Pitsidianakis [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=vmope.urd1m26bujz@linaro.org \
    --to=manos.pitsidianakis@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=kraxel@redhat.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 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).