From: Luiz Capitulino <lcapitulino@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: aliguori@us.ibm.com, lilei@linux.vnet.ibm.com,
qemu-devel@nongnu.org, qemu-stable@nongnu.org, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH 3/4] qemu-char: Register ring buffer driver with correct name "ringbuf"
Date: Wed, 3 Jul 2013 10:54:31 -0400 [thread overview]
Message-ID: <20130703105431.7629bf04@redhat.com> (raw)
In-Reply-To: <1372342930-28684-4-git-send-email-armbru@redhat.com>
On Thu, 27 Jun 2013 16:22:09 +0200
Markus Armbruster <armbru@redhat.com> wrote:
> The driver is new in 1.4, with the documented name "ringbuf".
> However, it's actual name is the completely undocumented "memory".
> Screwed up in commit 3949e59. Fix code to match documentation.
>
> Keep the undocumented name working as an alias for compatibility.
>
> Cc: qemu-stable@nongnu.org
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
This patch doesn't apply anymore, can you respin please?
> ---
> qemu-char.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/qemu-char.c b/qemu-char.c
> index a8fad65..968f572 100644
> --- a/qemu-char.c
> +++ b/qemu-char.c
> @@ -3755,7 +3755,7 @@ static void register_types(void)
> register_char_driver_qapi("null", CHARDEV_BACKEND_KIND_NULL, NULL);
> register_char_driver("socket", qemu_chr_open_socket);
> register_char_driver("udp", qemu_chr_open_udp);
> - register_char_driver_qapi("memory", CHARDEV_BACKEND_KIND_MEMORY,
> + register_char_driver_qapi("ringbuf", CHARDEV_BACKEND_KIND_MEMORY,
> qemu_chr_parse_ringbuf);
> register_char_driver_qapi("file", CHARDEV_BACKEND_KIND_FILE,
> qemu_chr_parse_file_out);
> @@ -3773,6 +3773,9 @@ static void register_types(void)
> register_char_driver_qapi("console", CHARDEV_BACKEND_KIND_CONSOLE, NULL);
> register_char_driver_qapi("pipe", CHARDEV_BACKEND_KIND_PIPE,
> qemu_chr_parse_pipe);
> + /* Bug-compatibility: */
> + register_char_driver_qapi("memory", CHARDEV_BACKEND_KIND_MEMORY,
> + qemu_chr_parse_ringbuf);
> }
>
> type_init(register_types);
next prev parent reply other threads:[~2013-07-03 15:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 14:22 [Qemu-devel] [PATCH 0/4] qemu-char: ringbuf fixes Markus Armbruster
2013-06-27 14:22 ` [Qemu-devel] [PATCH 1/4] qemu-char: Fix ringbuf option size Markus Armbruster
2013-06-27 23:17 ` Eric Blake
2013-07-03 14:54 ` Luiz Capitulino
2013-06-27 14:22 ` [Qemu-devel] [PATCH 2/4] Revert "chardev: Make the name of memory device consistent" Markus Armbruster
2013-06-28 3:35 ` Lei Li
2013-06-28 7:15 ` Markus Armbruster
2013-06-27 14:22 ` [Qemu-devel] [PATCH 3/4] qemu-char: Register ring buffer driver with correct name "ringbuf" Markus Armbruster
2013-07-03 14:54 ` Luiz Capitulino [this message]
2013-07-04 6:30 ` Markus Armbruster
2013-06-27 14:22 ` [Qemu-devel] [PATCH 4/4] qapi: Rename ChardevBackend member "memory" to "ringbuf" Markus Armbruster
2013-06-28 13:37 ` Eric Blake
2013-06-28 17:19 ` Markus Armbruster
2013-07-01 3:08 ` Amos Kong
2013-07-01 8:10 ` Markus Armbruster
2013-07-01 9:00 ` Amos Kong
2013-07-01 9:28 ` Markus Armbruster
2013-07-01 11:17 ` Amos Kong
2013-07-01 16:08 ` Markus Armbruster
2013-07-01 12:52 ` Anthony Liguori
2013-07-03 14:55 ` [Qemu-devel] [PATCH 0/4] qemu-char: ringbuf fixes Luiz Capitulino
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=20130703105431.7629bf04@redhat.com \
--to=lcapitulino@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=lilei@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).