mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: akpm@linux-foundation.org
Cc: andy.shevchenko@gmail.com, sergey.senozhatsky.work@gmail.com,
	hughd@google.com, uwe@kleine-koenig.org,
	jani.nikula@linux.intel.com, corbet@lwn.net,
	mike.kravetz@oracle.com, joe@perches.com,
	linux@rasmusvillemoes.dk, aarcange@redhat.com, pavel@ucw.cz,
	linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org
Subject: Re: + printf-add-support-for-printing-symbolic-error-codes.patch added to -mm tree
Date: Mon, 7 Oct 2019 10:14:11 +0200	[thread overview]
Message-ID: <20191007081411.fyvbvnjbvmpi4nla@pathway.suse.cz> (raw)
In-Reply-To: <20191005215200.OEG97MjOa%akpm@linux-foundation.org>

Hi Andrew,

On Sat 2019-10-05 14:52:00, Andrew Morton wrote:
> 
> The patch titled
>      Subject: vsprintf: add support for printing symbolic error codes
> has been added to the -mm tree.  Its filename is
>      printf-add-support-for-printing-symbolic-error-codes.patch

The patch is still under discussion. AFAIK, Rasmus is working on v4.
The main points are:

  + Rename the ambiguous "errcode" to "errname".

  + Introduce "%pe" instead of enhancing plain %p. First, the plain %p
    has become almost useless (hashing) on purpose (avoid leaking
    addresses). Second, we need something that will be explicitly
    used to print error codes.

  + Plus there are few more cosmetic issues.

I planed to take the patch via printk.git once ready.

Best Regards,
Petr

      reply	other threads:[~2019-10-07  8:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-05 21:52 akpm
2019-10-07  8:14 ` Petr Mladek [this message]

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=20191007081411.fyvbvnjbvmpi4nla@pathway.suse.cz \
    --to=pmladek@suse.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=corbet@lwn.net \
    --cc=hughd@google.com \
    --cc=jani.nikula@linux.intel.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=mike.kravetz@oracle.com \
    --cc=mm-commits@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --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®