qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pbonzini@redhat.com, armbru@redhat.com
Subject: [PATCH v2 0/3] char: Deprecate backend aliases
Date: Thu, 11 Mar 2021 17:42:50 +0100	[thread overview]
Message-ID: <20210311164253.338723-1-kwolf@redhat.com> (raw)

A small series from November that has fallen through the cracks...

These aliases only work the command line, but not in QMP. Command line
QAPIfication involves writing some compatibility glue for them, which
I'm doing, but I think it's desirable to unify accepted values of both
paths. So deprecate the aliases so that we can drop the compatibility
glue later.

v2:
- Don't mention deprecated options in the help [Markus]

- Added third patch to simplify the code again. Markus had suggested
  not complicating it in the first place, but then I would have to merge
  patches 1 and 2 even though they address different points, so this
  didn't feel very desirable.

Kevin Wolf (3):
  char: Skip CLI aliases in query-chardev-backends
  char: Deprecate backend aliases 'tty' and 'parport'
  char: Simplify chardev_name_foreach()

 docs/system/deprecated.rst |  6 ++++++
 chardev/char.c             | 19 +++++++++++--------
 2 files changed, 17 insertions(+), 8 deletions(-)

-- 
2.29.2



             reply	other threads:[~2021-03-11 16:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 16:42 Kevin Wolf [this message]
2021-03-11 16:42 ` [PATCH v2 1/3] char: Skip CLI aliases in query-chardev-backends Kevin Wolf
2021-03-11 16:42 ` [PATCH v2 2/3] char: Deprecate backend aliases 'tty' and 'parport' Kevin Wolf
2021-03-11 16:42 ` [PATCH v2 3/3] char: Simplify chardev_name_foreach() Kevin Wolf
2021-03-12  8:34 ` [PATCH v2 0/3] char: Deprecate backend aliases Markus Armbruster

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=20210311164253.338723-1-kwolf@redhat.com \
    --to=kwolf@redhat.com \
    --cc=armbru@redhat.com \
    --cc=pbonzini@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).