From: David Ahern <dsahern@gmail.com>
To: Namhyung Kim <namhyung.kim@lge.com>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>,
Namhyung Kim <namhyung@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFD] perf: Integrate logging facilities
Date: Mon, 12 Mar 2012 09:52:04 -0600 [thread overview]
Message-ID: <4F5E1BA4.2000209@gmail.com> (raw)
In-Reply-To: <4F5DC8D9.9030608@lge.com>
On 3/12/12 3:58 AM, Namhyung Kim wrote:
> This is a rough idea and there can be things I am missing. So I need to
> listen to your advices.
What Arnaldo proposed was having core, library code return error codes
and not print anything to the user. Higher layers (commands only?) can
take the return error code and pass it to perf_<subsystem>_strerror() to
dump a user friendly string for the error. See
http://lkml.org/lkml/2012/2/13/302
David
next prev parent reply other threads:[~2012-03-12 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 9:58 [RFD] perf: Integrate logging facilities Namhyung Kim
2012-03-12 15:52 ` David Ahern [this message]
2012-03-13 1:08 ` Namhyung Kim
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=4F5E1BA4.2000209@gmail.com \
--to=dsahern@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung.kim@lge.com \
--cc=namhyung@gmail.com \
--cc=paulus@samba.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