From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH] libxl: do not start dom0 qemu for stubdomain when not needed
Date: Fri, 28 Jul 2017 18:29:32 +0200 [thread overview]
Message-ID: <20170728162932.GR1095@mail-itl> (raw)
In-Reply-To: <22907.25480.717848.777692@mariner.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1510 bytes --]
On Fri, Jul 28, 2017 at 05:17:12PM +0100, Ian Jackson wrote:
> Wei Liu writes ("Re: [PATCH] libxl: do not start dom0 qemu for stubdomain when not needed"):
> > On Fri, Jul 28, 2017 at 06:05:13PM +0200, Marek Marczykowski-Górecki wrote:
> > > On Fri, Jul 28, 2017 at 04:17:51PM +0100, Wei Liu wrote:
> > > > On Thu, Jul 27, 2017 at 12:44:25AM +0200, Marek Marczykowski-Górecki wrote:
> > > > > + if (libxl_defbool_val(guest_config->b_info.u.hvm.vnc.enable) ||
> > > > > + libxl_defbool_val(guest_config->b_info.u.hvm.spice.enable) ||
> > > > > + libxl_defbool_val(guest_config->b_info.u.hvm.sdl.enable)) {
> > > >
> > > > Indentation.
> > >
> > > Should it really be indented at the same level as the code inside this
> > > block? Looks misleading (you need to look for ") {" to see where
> > > condition ends).
> >
> > That's how existing code in libxl is like, isn't it?
>
> Yes. Sadly.
>
> If you like we could have a bunfight about changing the indent level.
> I like 2, personally :-P.
>
> A compromise might be to move the || to the start of the next line, so
>
> if (cond1
> || cond2
> || cond3) {
> code1;
> code2;
>
> I have done that sometimes in libxl and no-one has objected.
Ok, it would be much better, thanks.
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-07-28 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 22:44 [PATCH] libxl: do not start dom0 qemu for stubdomain when not needed Marek Marczykowski-Górecki
2017-07-28 15:17 ` Wei Liu
2017-07-28 15:34 ` Marek Marczykowski-Górecki
2017-07-28 15:39 ` Wei Liu
2017-07-28 16:05 ` Marek Marczykowski-Górecki
2017-07-28 16:12 ` Wei Liu
2017-07-28 16:17 ` Ian Jackson
2017-07-28 16:29 ` Marek Marczykowski-Górecki [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=20170728162932.GR1095@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=ian.jackson@eu.citrix.com \
--cc=wei.liu2@citrix.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 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).