From: Alexandra Sava <alexandrasava18@gmail.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Anthony PERARD <anthony.perard@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] libxl: Cleanup, use LOG*, GCSPRINTF and CTX macros in libxl_device.c
Date: Tue, 5 Nov 2013 16:34:30 +0200 [thread overview]
Message-ID: <CAMFpKOhFWwaut1+c1-a_CXF-3RVSHe0_QB26vZH7-dcvM7j1hw@mail.gmail.com> (raw)
In-Reply-To: <1383659774.13961.72.camel@kazak.uk.xensource.com>
On 5 November 2013 15:56, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> On Tue, 2013-11-05 at 11:48 +0000, George Dunlap wrote:
>> > bad_format:
>> > - LIBXL__LOG(ctx, LIBXL__LOG_DEBUG, "Disk vdev=%s, backend %s"
>> > - " unsuitable due to format %s",
>> > - a->disk->vdev,
>> > - libxl_disk_backend_to_string(backend),
>> > - libxl_disk_format_to_string(a->disk->format));
>> > + LOG(DEBUG, "Disk vdev=%s, backend %s unsuitable due to format %s",
>> > + a->disk->vdev,
>> > + libxl_disk_backend_to_string(backend),
>> > + libxl_disk_format_to_string(a->disk->format));
>>
>> Given that in existing places, the LOG macro has formatted variables
>> aligned to the beginning of the quote rather than to the open paren,
>
> There's a bit of a mixture and the indented version is more prevalent.
> But there's only 7 multiline uses of LOG* in that file (the split is 5:2
> in favour of indentation).
>
> I'd object to just reindenting but if the line is changing anyway I have
> no strong feelings on the style used.
>
> The non-indented variant does have the benefit that formatting helpers
> (e.g. emacs' c-mode) do it that way for you...
>
> Ian.
>
>
Hi guys,
Thanks for the review. I will update the patch based on your suggestions:
* fix indentation stuff
* break lines up to 80 characters when necessary
* change commit message with:
Use new LOG* and GCSPRINTF macros in libxl_device.c
Replace libxl__sprintf, LIBXL__LOG and LIBXL__LOG_ERRNO with new
"Convenience macros": GCSPRINTF, LOG, LOGE
Thanks,
Alexandra
next prev parent reply other threads:[~2013-11-05 14:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 18:06 [PATCH] libxl: Cleanup, use LOG*, GCSPRINTF and CTX macros in libxl_device.c alexandrasava18
2013-11-04 18:33 ` Wei Liu
2013-11-04 21:43 ` Alexandra Sava
2013-11-05 11:48 ` George Dunlap
2013-11-05 12:02 ` Ian Campbell
2013-11-05 13:56 ` Ian Campbell
2013-11-05 14:34 ` Alexandra Sava [this message]
2013-11-05 16:55 ` [PATCH v2] libxl: Use new LOG* and GCSPRINTF " Alexandra Sava
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=CAMFpKOhFWwaut1+c1-a_CXF-3RVSHe0_QB26vZH7-dcvM7j1hw@mail.gmail.com \
--to=alexandrasava18@gmail.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=ian.jackson@eu.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).