All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Amit Shah <amit.shah@redhat.com>
Cc: qemu list <qemu-devel@nongnu.org>, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH REBASE/RESEND 2/4] virtio-serial: Add description fields for qdev properties
Date: Thu, 17 Feb 2011 07:11:44 -0600	[thread overview]
Message-ID: <4D5D1E90.4080501@codemonkey.ws> (raw)
In-Reply-To: <20110217130324.GC27487@amit-x200.redhat.com>

On 02/17/2011 07:03 AM, Amit Shah wrote:
> On (Tue) 15 Feb 2011 [10:10:23], Anthony Liguori wrote:
>
>    
>>> diff --git a/hw/virtio-serial.h b/hw/virtio-serial.h
>>> index a308196..2c5e336 100644
>>> --- a/hw/virtio-serial.h
>>> +++ b/hw/virtio-serial.h
>>> @@ -57,6 +57,19 @@ struct virtio_console_control {
>>>
>>>   /* == In-qemu interface == */
>>>
>>> +#define PROP_VIRTSERIAL_IS_CONSOLE_DESC                                 \
>>> +    "An hvc console will be spawned in the guest if this is set."
>>> +
>>> +#define PROP_VIRTSERIAL_NR_DESC                                         \
>>> +    "The 'number' for the port for predictable port numbers. Use this to " \
>>> +    "spawn ports if you plan to migrate the guest."
>>> +
>>> +#define PROP_VIRTSERIAL_CHR_DESC                \
>>> +    "The chardev to associate this port with."
>>> +
>>> +#define PROP_VIRTSERIAL_NAME_DESC                \
>>> +    "Name for the port that's exposed to the guest for port discovery."
>>> +
>>>        
>> Why are you using a #define instead of inlining the docs?
>>      
> These are shared by the generic and console ports.
>    

Are the properties the same?  Should a common properties define be used 
like with network and disk devices?

Regards,

Anthony Liguori

> 		Amit
>
>    

  reply	other threads:[~2011-02-17 13:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04  6:18 [Qemu-devel] [PATCH REBASE/RESEND 0/4] Auto-document qdev devices Amit Shah
2011-02-04  6:18 ` [Qemu-devel] [PATCH REBASE/RESEND 1/4] qdev: Add a description field for qdev properties for documentation Amit Shah
2011-02-15 16:43   ` Anthony Liguori
2011-02-17 13:06     ` Amit Shah
2011-02-17 13:12       ` Anthony Liguori
2011-02-17 13:37         ` Amit Shah
2011-02-18  8:59         ` Markus Armbruster
2011-02-18 15:21           ` Anthony Liguori
2011-02-18  8:54     ` Markus Armbruster
2011-02-04  6:18 ` [Qemu-devel] [PATCH REBASE/RESEND 2/4] virtio-serial: Add description fields for qdev properties Amit Shah
2011-02-15 16:10   ` Anthony Liguori
2011-02-17 13:03     ` Amit Shah
2011-02-17 13:11       ` Anthony Liguori [this message]
2011-02-17 13:39         ` Amit Shah
2011-02-04  6:18 ` [Qemu-devel] [PATCH REBASE/RESEND 3/4] net.h: Add description fields for qdev properites Amit Shah
2011-02-04  6:18 ` [Qemu-devel] [PATCH REBASE/RESEND 4/4] block_int.h: Provide documentation for common block qdev properties Amit Shah
2011-02-04  8:02 ` [Qemu-devel] [PATCH REBASE/RESEND 0/4] Auto-document qdev devices Markus Armbruster
2011-02-15 16:12 ` Anthony Liguori
2011-02-17 13:45   ` Amit Shah
2011-02-18  8:53   ` Markus Armbruster
2011-02-18 15:18     ` Anthony Liguori

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=4D5D1E90.4080501@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=amit.shah@redhat.com \
    --cc=armbru@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 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.