From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Kevin Tian <kevin.tian@intel.com>, Feng Wu <feng.wu@intel.com>
Subject: Re: [PATCH] VT-d: drop pointless uses of __func__
Date: Wed, 24 Aug 2016 16:30:38 -0400 [thread overview]
Message-ID: <20160824203038.GC23337@char.us.oracle.com> (raw)
In-Reply-To: <57BD6EC00200007800108794@prv-mh.provo.novell.com>
On Wed, Aug 24, 2016 at 01:54:08AM -0600, Jan Beulich wrote:
> Debugging message text already includes file name and line number, so
> also logging function names is redundant.
And you also fixed one style guide violation :-)
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-08-24 20:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 7:54 [PATCH] VT-d: drop pointless uses of __func__ Jan Beulich
2016-08-24 20:30 ` Konrad Rzeszutek Wilk [this message]
2016-08-25 1:05 ` Tian, Kevin
2016-08-25 1:08 ` Wu, Feng
2016-08-25 6:44 ` Jan Beulich
2016-08-25 7:52 ` Wu, Feng
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=20160824203038.GC23337@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=feng.wu@intel.com \
--cc=kevin.tian@intel.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 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).