From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Stefan Weil" <sw@weilnetz.de>,
"Volker Rümelin" <vr_qemu@t-online.de>,
clamky@hotmail.com, "Yonggang Luo" <luoyonggang@gmail.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Kővágó Zoltán" <dirty.ice.hu@gmail.com>
Subject: Re: [PATCH 1/3] MAINTAINERS: Split Audio backends VS frontends
Date: Wed, 18 Aug 2021 14:48:37 +0200 [thread overview]
Message-ID: <4074977.GUTxnQdd72@silver> (raw)
In-Reply-To: <0d7f824c-8392-9a94-90be-befa45b3a722@redhat.com>
On Dienstag, 17. August 2021 19:57:21 CEST Philippe Mathieu-Daudé wrote:
> On 8/17/21 6:12 PM, Christian Schoenebeck wrote:
> > On Dienstag, 17. August 2021 14:41:27 CEST Gerd Hoffmann wrote:
> >> Hi,
> >>
> >>>> +Overall Audio frontends
> >>>
> >>> I would call that "Audio Hardware Emulation" instead of "Overall Audio
> >>> frontends".
> >>>
> >>>> +Overall Audio backends
> >>>
> >>> Likewise I would call this section "Shared/common QEMU audio library/
> >>> subsystem" or something like that instead of "Overall Audio backends".
> >>
> >> Well, frontend/backend is common qemu terminology, with "frontend" being
> >> the emulated/virtual device as seen by the guest and "backend" being the
> >> host-side wireup (i.e. -audiodev / -blockdev / -chardev / -netdev / ...)
> >>
> >> take care,
> >>
> >> Gerd
> >
> > Yeah, I was seeing this (like usual) more from an external/new developer
> > perspective where the semantic for "frontend"/"backend" is not that
> > obvious
> > here.
>
> "Audio Backends" is in the "Subsystems" meta-section, and
> "Audio Frontends" in the "Devices" one.
>
> Maybe we using the === separator for meta-sections (like rST)
> instead of --- would help seeing the difference.
No need for now. On the long-term the MAINTAINERS structure might be improved
in some way to make specific tree structures more clear, but for now it's Ok.
Thanks!
Best regards,
Christian Schoenebeck
next prev parent reply other threads:[~2021-08-18 12:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 19:10 [PATCH 0/3] MAINTAINERS: Split Audio section Philippe Mathieu-Daudé
2021-08-16 19:10 ` [PATCH 1/3] MAINTAINERS: Split Audio backends VS frontends Philippe Mathieu-Daudé
2021-08-17 11:31 ` Christian Schoenebeck
2021-08-17 12:41 ` Gerd Hoffmann
2021-08-17 16:12 ` Christian Schoenebeck
2021-08-17 17:57 ` Philippe Mathieu-Daudé
2021-08-18 12:48 ` Christian Schoenebeck [this message]
2021-08-16 19:10 ` [PATCH 2/3] MAINTAINERS: Remove SPICE from Audio backends section Philippe Mathieu-Daudé
2021-08-17 11:32 ` Christian Schoenebeck
2021-08-16 19:10 ` [PATCH 3/3] MAINTAINERS: Split Audio backends sections Philippe Mathieu-Daudé
2021-08-17 11:41 ` Christian Schoenebeck
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=4074977.GUTxnQdd72@silver \
--to=qemu_oss@crudebyte.com \
--cc=clamky@hotmail.com \
--cc=dirty.ice.hu@gmail.com \
--cc=kraxel@redhat.com \
--cc=luoyonggang@gmail.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
--cc=vr_qemu@t-online.de \
/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).