From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Keir Fraser <keir@xen.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>
Subject: Re: [PATCH 2/2] make {,g}dprintk() a no‑op in non‑debug builds
Date: Tue, 24 Mar 2015 14:19:29 +0000 [thread overview]
Message-ID: <1427206769.21742.401.camel@citrix.com> (raw)
In-Reply-To: <550C4717020000780006C1C5@mail.emea.novell.com>
On Fri, 2015-03-20 at 15:13 +0000, Jan Beulich wrote:
> As discussed before, code absolutely wanting to get something into the
> log should use {,g}printk() instead.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Ian Campbell <ian.campbell@citrix.com>
next prev parent reply other threads:[~2015-03-24 14:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 15:04 [PATCH 0/2] printk adjustments Jan Beulich
2015-03-20 15:12 ` [PATCH 1/2] introduce gprintk() Jan Beulich
2015-03-24 14:20 ` Ian Campbell
2015-03-24 15:12 ` Julien Grall
2015-03-24 15:31 ` Jan Beulich
2015-03-24 15:36 ` Julien Grall
2015-03-24 15:42 ` Ian Campbell
2015-03-20 15:13 ` [PATCH 2/2] make {,g}dprintk() a no‑op in non‑debug builds Jan Beulich
2015-03-24 14:19 ` Ian Campbell [this message]
2015-03-25 17:26 ` [PATCH 0/2] printk adjustments Andrew Cooper
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=1427206769.21742.401.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--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.