From: Randy Dunlap <rdunlap@infradead.org>
To: "Enrico Weigelt, metux IT consult" <enrico.weigelt@gr13.net>,
Joe Perches <joe@perches.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lib: vsprintf: add printf format conversion %M for errno strings
Date: Sun, 25 Jun 2017 15:47:45 -0700 [thread overview]
Message-ID: <3a8df2e2-114c-9f2c-325a-49f234726b08@infradead.org> (raw)
In-Reply-To: <71909969-b6be-d116-3372-7add409c1ec1@gr13.net>
On 06/25/2017 02:18 PM, Enrico Weigelt, metux IT consult wrote:
> On 25.06.2017 22:10, Joe Perches wrote:
>
>>> Yeah, that's still an open problem. Actually, I still haven't found out,
>>> how it's done w/ all the other kernel-internal conversions.
>>
>> Everything else uses "%p<foo>", <object reference>
>
> hmm, but errno's aren't pointers. Isn't %p checked for pointer values ?
>>> Already was about to do so. Shall I call it strerror() ?
>>
>> I presume kstrerror
>>
>> So use something like
>> "%d: (%s)", errno, kstrerror(errno)
>
> Okay, sounds good.
but why not just do that in userspace. Sure, you can keep that as your
internal kernel patch, but there's not really much need for it to be in the
mainline kernel. So when your driver prints "blah: foo bar error 49",
just run a little program that converts 49 to <whatever>.
--
~Randy
next prev parent reply other threads:[~2017-06-25 22:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-25 17:12 Enrico Weigelt, metux IT consult
2017-06-25 17:24 ` Randy Dunlap
2017-06-25 17:27 ` Joe Perches
2017-06-25 19:53 ` Enrico Weigelt, metux IT consult
2017-06-25 20:10 ` Joe Perches
2017-06-25 21:18 ` Enrico Weigelt, metux IT consult
2017-06-25 22:47 ` Randy Dunlap [this message]
2017-06-26 0:42 ` Enrico Weigelt, metux IT consult
2017-06-27 11:02 ` Bernd Petrovitsch
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=3a8df2e2-114c-9f2c-325a-49f234726b08@infradead.org \
--to=rdunlap@infradead.org \
--cc=enrico.weigelt@gr13.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.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®