From: Joe Perches <joe@perches.com>
To: "Uwe Kleine-König" <uwe@kleine-koenig.org>,
"Sergey Senozhatsky" <sergey.senozhatsky.work@gmail.com>,
"Jani Nikula" <jani.nikula@linux.intel.com>,
"Petr Mladek" <pmladek@suse.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
Enrico@kleine-koenig.org, Weigelt@kleine-koenig.org,
"metux IT consult" <lkml@metux.net>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] vsprintf: introduce %dE for error constants
Date: Tue, 27 Aug 2019 14:22:09 -0700 [thread overview]
Message-ID: <04b021b263465c62628964ac402e15fd4cdc13a0.camel@perches.com> (raw)
In-Reply-To: <20190827211244.7210-1-uwe@kleine-koenig.org>
On Tue, 2019-08-27 at 23:12 +0200, Uwe Kleine-König wrote:
> The new format specifier %dE introduced with this patch pretty-prints
> the typical negative error values. So
>
> pr_info("probing failed (%dE)\n", ret);
>
> yields
>
> probing failed (EIO)
>
> if ret holds -EIO. This is easier to understand than the for now common
>
> probing failed (-5)
I suggest using both outputs like '-5 -EIO'
rather than a single string
next prev parent reply other threads:[~2019-08-27 21:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 21:12 Uwe Kleine-König
2019-08-27 21:17 ` Uwe Kleine-König
2019-08-27 21:22 ` Joe Perches [this message]
2019-08-27 21:35 ` Uwe Kleine-König
2019-08-27 23:10 ` Joe Perches
2019-08-28 11:32 ` Petr Mladek
2019-08-28 11:54 ` Jani Nikula
2019-08-28 12:02 ` Sergey Senozhatsky
2019-08-28 12:49 ` Rasmus Villemoes
2019-08-28 12:59 ` Sergey Senozhatsky
2019-08-28 16:22 ` Uwe Kleine-König
2019-08-29 0:27 ` Sergey Senozhatsky
2019-08-28 19:18 ` Uwe Kleine-König
2019-08-29 8:12 ` Petr Mladek
2019-08-29 8:27 ` Juergen Gross
2019-08-29 9:09 ` Rasmus Villemoes
2019-08-29 17:39 ` Uwe Kleine-König
2019-08-30 9:06 ` Petr Mladek
2019-08-30 15:47 ` Uwe Kleine-König
2019-08-30 21:45 ` Rasmus Villemoes
2019-08-29 9:00 ` Rasmus Villemoes
2019-08-28 19:59 ` Uwe Kleine-König
2019-08-28 20:51 ` Mark Brown
2019-08-29 13:39 ` Andy Shevchenko
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=04b021b263465c62628964ac402e15fd4cdc13a0.camel@perches.com \
--to=joe@perches.com \
--cc=Enrico@kleine-koenig.org \
--cc=Weigelt@kleine-koenig.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metux.net \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=uwe@kleine-koenig.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
all inboxes | Powered by JetHome®