From: Kelley Nielsen <kelleynnn@gmail.com>
To: xen-devel@lists.xensource.com
Cc: anthony.perard@citrix.com, Ian.Campbell@citrix.com
Subject: [PATCH OPW 0/0] Resend of macro coding style fixes needing reindents
Date: Mon, 11 Nov 2013 07:50:07 -0800 [thread overview]
Message-ID: <1384185014-30342-1-git-send-email-kelleynnn@gmail.com> (raw)
These patches all use the convenience macros defined in libxl_internals.h
to replace the old style. I've been asked to correct indentation errors
that were present in the first versions and resend them all as a set.
[PATCH OPW 1/7] libxl: Use new macro LOGE() in libxl_qmp.c
[PATCH OPW 2/7] libxl: replace last invocation of LIBXL__LOG_ERROR
[PATCH OPW 3/7] libxl: use GCSPRINTF in place of libxl_sprintf() in
[PATCH OPW 4/7] libxl: use GCSPRINTF instead of libxl__sprintf
[PATCH OPW 5/7] libxl: use LOGE instead of LIBXL__LOG_ERRNO in
[PATCH OPW 6/7] libxl: use LOG and LOGE instead of LIBXL__LOG* in
[PATCH OPW 7/7] libxl: use LOG instead of LIBXL__LOG in libxl_utils.c
next reply other threads:[~2013-11-11 15:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 15:50 Kelley Nielsen [this message]
2013-11-11 15:50 ` [PATCH OPW 1/7] libxl: Use new macro LOGE() in libxl_qmp.c Kelley Nielsen
2013-11-11 16:56 ` Ian Campbell
2013-11-11 15:50 ` [PATCH OPW 2/7] libxl: replace last invocation of LIBXL__LOG_ERROR with LOGE Kelley Nielsen
2013-11-11 15:50 ` [PATCH OPW 3/7] libxl: use GCSPRINTF in place of libxl_sprintf() in libxl_qmp.c Kelley Nielsen
2013-11-11 16:58 ` Ian Campbell
2013-11-11 15:50 ` [PATCH OPW 4/7] libxl: use GCSPRINTF instead of libxl__sprintf Kelley Nielsen
2013-11-11 15:50 ` [PATCH OPW 5/7] libxl: use LOGE instead of LIBXL__LOG_ERRNO in libxl_utils.c Kelley Nielsen
2013-11-11 15:50 ` [PATCH OPW 6/7] libxl: use LOG and LOGE instead of LIBXL__LOG* " Kelley Nielsen
2013-11-11 15:50 ` [PATCH OPW 7/7] libxl: use LOG instead of LIBXL__LOG " Kelley Nielsen
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=1384185014-30342-1-git-send-email-kelleynnn@gmail.com \
--to=kelleynnn@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=anthony.perard@citrix.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).