From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 6/18 V2]: PVH xen: Introduce PVH guest type
Date: Tue, 19 Mar 2013 09:03:41 -0400 [thread overview]
Message-ID: <20130319130341.GB2706@phenom.dumpdata.com> (raw)
In-Reply-To: <5148348502000078000C6A17@nat28.tlf.novell.com>
On Tue, Mar 19, 2013 at 08:48:53AM +0000, Jan Beulich wrote:
> >>> On 19.03.13 at 01:21, Mukesh Rathor <mukesh.rathor@oracle.com> wrote:
> > On Mon, 18 Mar 2013 11:54:29 +0000
> > "Jan Beulich" <JBeulich@suse.com> wrote:
> >
> >> >>> On 16.03.13 at 01:32, Mukesh Rathor <mukesh.rathor@oracle.com>
> >> >>> wrote:
> >> > @@ -277,8 +280,8 @@ struct domain
> >> > struct rangeset *iomem_caps;
> >> > struct rangeset *irq_caps;
> >> >
> >> > - /* Is this an HVM guest? */
> >> > - bool_t is_hvm;
> >> > + /* !is_pvh && !is_hvm ==> PV, else PVH or HVM */
> >> > + enum {hvm_guest=1, pvh_guest} guest_type;
> >>
> >> And of course, please properly format this.
> >
> > Not sure I follow what needs formatting?
>
> A number of blanks need to be inserted. And the whole enum
> declaration probably doesn't belong on a single line anyway.
The single line looks to be already there:
enum { DOMDYING_alive, DOMDYING_dying, DOMDYING_dead } is_dying;
So I think Mukesh is just following the same convention in that
file. Should he depart from it?
next prev parent reply other threads:[~2013-03-19 13:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-16 0:32 [PATCH 6/18 V2]: PVH xen: Introduce PVH guest type Mukesh Rathor
2013-03-18 11:54 ` Jan Beulich
2013-03-19 0:21 ` Mukesh Rathor
2013-03-19 8:48 ` Jan Beulich
2013-03-19 13:03 ` Konrad Rzeszutek Wilk [this message]
2013-03-19 13:41 ` Jan Beulich
2013-03-23 1:13 ` Mukesh Rathor
2013-03-25 9:26 ` Jan Beulich
2013-03-25 19:05 ` Mukesh Rathor
2013-03-25 20:07 ` Keir Fraser
2013-03-25 22:04 ` Mukesh Rathor
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=20130319130341.GB2706@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.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.