From: David Vrabel <david.vrabel@citrix.com>
To: Kelley Nielsen <kelleynnn@gmail.com>
Cc: xen-devel@lists.xensource.com, Ian.Campbell@citrix.com
Subject: Re: [PATCH 0/4] Compliance with new coding style
Date: Mon, 11 Nov 2013 12:54:00 +0000 [thread overview]
Message-ID: <5280D368.5060208@citrix.com> (raw)
In-Reply-To: <1384153707-24240-1-git-send-email-kelleynnn@gmail.com>
On 11/11/13 07:08, Kelley Nielsen wrote:
> This patchset brings the file libxl_utils.c mostly into compliance
> with the new coding style involving the convenience macros LOG,
> LOGE, and GCSPRINTF.
>
> [PATCH 1/4] opw: libxl: use GCSPRINTF instead of libxl__sprintf
> [PATCH 2/4] opw: libxl: use LOGE instead of LIBXL__LOG_ERRNO in
> [PATCH 3/4] opw: libxl: use LOG and LOGE instead of LIBXL__LOG* in
> [PATCH 4/4] opw: libxl: use LOG instead of LIBXL__LOG in
I think you should drop the "opw:" prefix from the subject.
David
next prev parent reply other threads:[~2013-11-11 12:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 7:08 [PATCH 0/4] Compliance with new coding style Kelley Nielsen
2013-11-11 7:08 ` [PATCH 1/4] opw: libxl: use GCSPRINTF instead of libxl__sprintf Kelley Nielsen
2013-11-11 12:27 ` Ian Campbell
2013-11-11 7:08 ` [PATCH 2/4] opw: libxl: use LOGE instead of LIBXL__LOG_ERRNO in libxl_utils.c Kelley Nielsen
2013-11-11 12:28 ` Ian Campbell
2013-11-11 7:08 ` [PATCH 3/4] opw: libxl: use LOG and LOGE instead of LIBXL__LOG* " Kelley Nielsen
2013-11-11 12:28 ` Ian Campbell
2013-11-11 7:08 ` [PATCH 4/4] opw: libxl: use LOG instead of LIBXL__LOG " Kelley Nielsen
2013-11-11 12:30 ` Ian Campbell
2013-11-11 12:54 ` David Vrabel [this message]
2013-11-11 13:11 ` [PATCH 0/4] Compliance with new coding style Kelley Nielsen
2013-11-11 14:10 ` Konrad Rzeszutek Wilk
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=5280D368.5060208@citrix.com \
--to=david.vrabel@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=kelleynnn@gmail.com \
--cc=xen-devel@lists.xensource.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 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).