All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>, Wei Liu <wei.liu2@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 0/4] libxl: use LOG() macro where appropriate
Date: Tue, 15 Sep 2015 16:16:58 +0100	[thread overview]
Message-ID: <1442330218.18856.1.camel@citrix.com> (raw)
In-Reply-To: <22008.12365.255490.89666@mariner.uk.xensource.com>

On Tue, 2015-09-15 at 15:50 +0100, Ian Jackson wrote:
> Wei Liu writes ("[PATCH 0/4] libxl: use LOG() macro where appropriate"):
> > There are mixed usage of different logging macros. Ideally we only use
> > one
> > style to avoid confusion.
> 
> All four
> 
> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>

In terms of applying it seems like the sort of thing which would cause a
lot of pain for backports to 4.6. Shall we hold off or do we think the
inflow of backports has slowed sufficiently now?

Ian.

  reply	other threads:[~2015-09-15 15:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15  9:41 [PATCH 0/4] libxl: use LOG() macro where appropriate Wei Liu
2015-09-15  9:41 ` [PATCH 1/4] libxl: convert to use LOG() macro Wei Liu
2015-09-15 15:12   ` Andrew Cooper
2015-09-15 15:36     ` Wei Liu
2015-09-15 17:01     ` Ian Jackson
2015-09-15  9:41 ` [PATCH 2/4] libxl: fix overly lines and delete extraneous quotes Wei Liu
2015-09-15  9:41 ` [PATCH 3/4] libxl: map LIBXL__LOG_VERBOSE to XTL_VERBOSE Wei Liu
2015-09-15  9:41 ` [PATCH 4/4] libxl: fix places missed by spatch Wei Liu
2015-09-15 14:50 ` [PATCH 0/4] libxl: use LOG() macro where appropriate Ian Jackson
2015-09-15 15:16   ` Ian Campbell [this message]
2015-09-15 15:37     ` Wei Liu
2015-09-15 17:01     ` Ian Jackson

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=1442330218.18856.1.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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.