From: Roman Penyaev <r.peniaev@gmail.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v5 0/8] chardev: implement backend chardev multiplexing
Date: Thu, 31 Oct 2024 13:10:39 +0100 [thread overview]
Message-ID: <CACZ9PQV5ZkKsCJRd5U8aj1B0txmPyha3CQDHeM3j75Kj4hJWfg@mail.gmail.com> (raw)
In-Reply-To: <CAJ+F1CKtXFiYyoT3QkubESiTUo4VxYt2Ed0g_QjgU8YasAeZjw@mail.gmail.com>
On Thu, Oct 31, 2024 at 12:34 PM Marc-André Lureau
<marcandre.lureau@gmail.com> wrote:
>
> Hi Roman
>
> On Thu, Oct 31, 2024 at 3:12 PM Roman Penyaev <r.peniaev@gmail.com> wrote:
>>
>> Hi Marc-André,
>>
>> In this 5th version of the mux-be series it seems I addressed all the
>> comments and concerns. Could you please take a look once again?
>>
>
> I am not sure adding a "mux-be-id" option to all chardevs is the way to go. To me it feels like working around the issue that arrays are not supported on the CLI.
With CLI it seems not a problem: you can always use the ',,' sequence, or we
can introduce another separator, for example ':'. With JSON I could not find
a working array example, but probably the same trick with any separator in a
string can work as well. What do you think?
> I would like others to comment..
Probably makes sense to ping them once again.
--
Roman
prev parent reply other threads:[~2024-10-31 12:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 14:43 [PATCH v5 0/8] chardev: implement backend chardev multiplexing Roman Penyaev
2024-10-17 14:43 ` [PATCH v5 1/8] chardev/char: rename `MuxChardev` struct to `MuxFeChardev` Roman Penyaev
2024-10-17 14:43 ` [PATCH v5 2/8] chardev/char: rename `char-mux.c` to `char-mux-fe.c` Roman Penyaev
2024-10-17 14:43 ` [PATCH v5 3/8] chardev/char: move away mux suspend/resume calls Roman Penyaev
2024-10-17 14:43 ` [PATCH v5 4/8] chardev/char: rename frontend mux calls Roman Penyaev
2024-10-17 14:43 ` [PATCH v5 5/8] chardev/char: introduce `mux-be-id=ID` option Roman Penyaev
2024-10-17 14:43 ` [PATCH v5 6/8] chardev/char-mux: implement backend chardev multiplexing Roman Penyaev
2024-10-17 14:43 ` [PATCH v5 7/8] tests/unit/test-char: add unit test for the `mux-be` multiplexer Roman Penyaev
2024-10-17 14:43 ` [PATCH v5 8/8] qemu-options.hx: describe multiplexing of several backend devices Roman Penyaev
2024-10-31 11:09 ` [PATCH v5 0/8] chardev: implement backend chardev multiplexing Roman Penyaev
2024-10-31 11:34 ` Marc-André Lureau
2024-10-31 12:10 ` Roman Penyaev [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=CACZ9PQV5ZkKsCJRd5U8aj1B0txmPyha3CQDHeM3j75Kj4hJWfg@mail.gmail.com \
--to=r.peniaev@gmail.com \
--cc=marcandre.lureau@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 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).