Ian Campbell writes ("Re: [PATCH 0/4] libxl: use LOG() macro where
appropriate"):
> 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?
I would like to
There are mixed usage of different logging macros. Ideally we only use one
style to avoid confusion.
Wei Liu (4):
libxl: convert to use LOG() macro
libxl: fix overly lines and delete extraneous quotes
libxl: map LIBXL__LOG_VERBOSE to XTL_VERBOSE
libxl: fix places missed by spatch
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
On Tue, Sep 15, 2015 at 04:16:58PM +0100, Ian Campbell wrote:
> 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
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
___
Xen-devel