[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <04b021b263465c62628964ac402e15fd4cdc13a0.camel@perches.com>
Date: Tue, 27 Aug 2019 14:22:09 -0700
From: Joe Perches <joe@...ches.com>
To: Uwe Kleine-König <uwe@...ine-koenig.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
Jani Nikula <jani.nikula@...ux.intel.com>,
Petr Mladek <pmladek@...e.com>,
Steven Rostedt <rostedt@...dmis.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Enrico@...ine-koenig.org, Weigelt@...ine-koenig.org,
metux IT consult <lkml@...ux.net>
Cc: Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] vsprintf: introduce %dE for error constants
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
Powered by blists - more mailing lists