From: Zhao Liu <zhao1.liu@intel.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org, qemu-trivial@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [PATCH trivial] chardev/char.c: fix "abstract device type" error message
Date: Wed, 3 Jan 2024 22:16:40 +0800 [thread overview]
Message-ID: <ZZVsSGz5YsEfUBBc@intel.com> (raw)
In-Reply-To: <20240103114221.325221-1-mjt@tls.msk.ru>
On Wed, Jan 03, 2024 at 02:42:21PM +0300, Michael Tokarev wrote:
> Date: Wed, 3 Jan 2024 14:42:21 +0300
> From: Michael Tokarev <mjt@tls.msk.ru>
> Subject: [PATCH trivial] chardev/char.c: fix "abstract device type" error
> message
> X-Mailer: git-send-email 2.39.2
>
> Current error message:
>
> qemu-system-x86_64: -chardev spice,id=foo: Parameter 'driver' expects an abstract device type
>
> while in fact the meaning is in reverse, -chardev expects
> a non-abstract device type.
>
> Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
> Fixes: 777357d758d9 "chardev: qom-ify" (2016-12-07)
> ---
Reviewed-by: Zhao Liu <zhao1.liu@intel.com>
> chardev/char.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/chardev/char.c b/chardev/char.c
> index 996a024c7a..119b548784 100644
> --- a/chardev/char.c
> +++ b/chardev/char.c
> @@ -518,7 +518,7 @@ static const ChardevClass *char_get_class(const char *driver, Error **errp)
>
> if (object_class_is_abstract(oc)) {
> error_setg(errp, QERR_INVALID_PARAMETER_VALUE, "driver",
> - "an abstract device type");
> + "a non-abstract device type");
> return NULL;
> }
>
> --
> 2.39.2
>
>
prev parent reply other threads:[~2024-01-03 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 11:42 [PATCH trivial] chardev/char.c: fix "abstract device type" error message Michael Tokarev
2024-01-03 14:16 ` Zhao Liu [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=ZZVsSGz5YsEfUBBc@intel.com \
--to=zhao1.liu@intel.com \
--cc=marcandre.lureau@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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 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.