From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: "Petr Mladek" <pmladek@suse.com>,
"Uwe Kleine-König" <uwe@kleine-koenig.org>,
"Sergey Senozhatsky" <sergey.senozhatsky.work@gmail.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
Enrico@kleine-koenig.org, Weigelt@kleine-koenig.org,
"Andrew Morton" <akpm@linux-foundation.org>,
"metux IT consult" <lkml@metux.net>,
"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: Wed, 28 Aug 2019 21:02:46 +0900 [thread overview]
Message-ID: <20190828120246.GA31416@jagdpanzerIV> (raw)
In-Reply-To: <87o9097bff.fsf@intel.com>
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
next prev parent reply other threads:[~2019-08-28 12:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 21:12 [PATCH v2] vsprintf: introduce %dE for error constants Uwe Kleine-König
2019-08-27 21:17 ` Uwe Kleine-König
2019-08-27 21:22 ` Joe Perches
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 [this message]
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=20190828120246.GA31416@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.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=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