[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190828120246.GA31416@jagdpanzerIV>
Date: Wed, 28 Aug 2019 21:02:46 +0900
From: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
To: Jani Nikula <jani.nikula@...ux.intel.com>
Cc: Petr Mladek <pmladek@...e.com>,
Uwe Kleine-König <uwe@...ine-koenig.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
Steven Rostedt <rostedt@...dmis.org>, Enrico@...ine-koenig.org,
Weigelt@...ine-koenig.org,
Andrew Morton <akpm@...ux-foundation.org>,
metux IT consult <lkml@...ux.net>,
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 (08/28/19 14:54), Jani Nikula wrote:
[..]
> > I personally think that this feature is not worth the code, data,
> > and bikeshedding.
>
> The obvious alternative, I think already mentioned, is to just add
> strerror() or similar as a function. I doubt there'd be much opposition
> to that. Folks could use %s and strerr(ret). And a follow-up could add
> the special format specifier if needed.
Yeah, I'd say that strerror() would be a better alternative
to vsprintf() specifier. (if we decide to add such functionality).
-ss
Powered by blists - more mailing lists