qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Thomas Huth <thuth@redhat.com>, Peter Maydell <peter.maydell@linaro.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	qemu-devel@nongnu.org, "Eduardo Habkost" <eduardo@habkost.net>,
	"David Hildenbrand" <david@redhat.com>
Subject: Re: [PATCH] qom/object: Limit type names to alphanumerical and some few special characters
Date: Thu, 16 Nov 2023 14:21:17 +0100	[thread overview]
Message-ID: <862c25dd-1393-4ffd-9880-2e405ec037ca@linaro.org> (raw)
In-Reply-To: <e04933cf-1c74-4475-8007-888d9d0591f2@redhat.com>

On 16/11/23 12:17, Thomas Huth wrote:
> On 14/11/2023 14.21, Peter Maydell wrote:
>> On Tue, 14 Nov 2023 at 13:05, Thomas Huth <thuth@redhat.com> wrote:

> There just seem to be two stragglers left:
> 
> 1) #define TYPE_DUMMY "qemu:dummy" in tests/unit/test-io-task.c ...
>     easy to fix, it's just a unit test anyway
> 
> 2) #define TYPE_RAM_DISCARD_MANAGER "qemu:ram-discard-manager"
>     in include/exec/memory.h ... I believe it should be OK to
>     simply rename it, since it's about an interface type...
>     Or do we use these interface names in migration streams, too?

No, QOM interfaces aren't part of any state, so not migrated.



      parent reply	other threads:[~2023-11-16 13:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14 13:04 [PATCH] qom/object: Limit type names to alphanumerical and some few special characters Thomas Huth
2023-11-14 13:21 ` Peter Maydell
2023-11-16 11:17   ` Thomas Huth
2023-11-16 11:37     ` Peter Maydell
2023-11-16 13:21     ` Philippe Mathieu-Daudé [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=862c25dd-1393-4ffd-9880-2e405ec037ca@linaro.org \
    --to=philmd@linaro.org \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=david@redhat.com \
    --cc=eduardo@habkost.net \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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).