All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Alistair Francis <alistair.francis@xilinx.com>,
	qemu-devel@nongnu.org, qemu-trivial@nongnu.org,
	Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH v2] hw/core/or-irq: Mark the device with cannot_instantiate_with_device_add_yet
Date: Fri, 03 Feb 2017 10:09:03 +0100	[thread overview]
Message-ID: <87lgtnd4k0.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <1485778972-20924-1-git-send-email-thuth@redhat.com> (Thomas Huth's message of "Mon, 30 Jan 2017 13:22:52 +0100")

Thomas Huth <thuth@redhat.com> writes:

> The "or-irq" device needs to be wired up in source code, there is no
> way the user can add this device with the "-device" parameter or the
> "device_add" monitor command yet.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  v2: Changed patch description and comment
>
>  hw/core/or-irq.c | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/hw/core/or-irq.c b/hw/core/or-irq.c
> index 1ac090d..808c8d1 100644
> --- a/hw/core/or-irq.c
> +++ b/hw/core/or-irq.c
> @@ -89,6 +89,9 @@ static void or_irq_class_init(ObjectClass *klass, void *data)
>      dc->props = or_irq_properties;
>      dc->realize = or_irq_realize;
>      dc->vmsd = &vmstate_or_irq;
> +
> +    /* Reason: Needs to be wired up in source code, e.g. see stm32f205_soc.c */

This line is a bit long, and it could be shortened easily: drop "in
source code", or replace it by "to work".  This is how similar comments
elsewhere are phrased.

> +    dc->cannot_instantiate_with_device_add_yet = true;
>  }
>  
>  static const TypeInfo or_irq_type_info = {

Preferably with the comment touched up:
Reviewed-by: Markus Armbruster <armbru@redhat.com>


WARNING: multiple messages have this Message-ID (diff)
From: Markus Armbruster <armbru@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Alistair Francis <alistair.francis@xilinx.com>,
	qemu-devel@nongnu.org, qemu-trivial@nongnu.org,
	Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v2] hw/core/or-irq: Mark the device with cannot_instantiate_with_device_add_yet
Date: Fri, 03 Feb 2017 10:09:03 +0100	[thread overview]
Message-ID: <87lgtnd4k0.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <1485778972-20924-1-git-send-email-thuth@redhat.com> (Thomas Huth's message of "Mon, 30 Jan 2017 13:22:52 +0100")

Thomas Huth <thuth@redhat.com> writes:

> The "or-irq" device needs to be wired up in source code, there is no
> way the user can add this device with the "-device" parameter or the
> "device_add" monitor command yet.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  v2: Changed patch description and comment
>
>  hw/core/or-irq.c | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/hw/core/or-irq.c b/hw/core/or-irq.c
> index 1ac090d..808c8d1 100644
> --- a/hw/core/or-irq.c
> +++ b/hw/core/or-irq.c
> @@ -89,6 +89,9 @@ static void or_irq_class_init(ObjectClass *klass, void *data)
>      dc->props = or_irq_properties;
>      dc->realize = or_irq_realize;
>      dc->vmsd = &vmstate_or_irq;
> +
> +    /* Reason: Needs to be wired up in source code, e.g. see stm32f205_soc.c */

This line is a bit long, and it could be shortened easily: drop "in
source code", or replace it by "to work".  This is how similar comments
elsewhere are phrased.

> +    dc->cannot_instantiate_with_device_add_yet = true;
>  }
>  
>  static const TypeInfo or_irq_type_info = {

Preferably with the comment touched up:
Reviewed-by: Markus Armbruster <armbru@redhat.com>

  reply	other threads:[~2017-02-03  9:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30 12:22 [Qemu-trivial] [PATCH v2] hw/core/or-irq: Mark the device with cannot_instantiate_with_device_add_yet Thomas Huth
2017-01-30 12:22 ` [Qemu-devel] " Thomas Huth
2017-02-03  9:09 ` Markus Armbruster [this message]
2017-02-03  9:09   ` Markus Armbruster
2017-02-03  9:15   ` [Qemu-trivial] " Markus Armbruster
2017-02-03  9:15     ` 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=87lgtnd4k0.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=alistair.francis@xilinx.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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 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.