All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org, senozhatsky@chromium.org,
	rostedt@goodmis.org, pmladek@suse.com, linux@rasmusvillemoes.dk,
	glider@google.com, elver@google.com, dvyukov@google.com,
	akpm@linux-foundation.org
Subject: Re: + lib-vsprintf-split-out-sprintf-and-friends.patch added to mm-nonmm-unstable branch
Date: Tue, 15 Aug 2023 17:39:08 +0300	[thread overview]
Message-ID: <ZNuODCU2i0Mr2l8R@smile.fi.intel.com> (raw)
In-Reply-To: <893b27ec-3f78-47fc-8298-903f991d5aaa@p183>

On Tue, Aug 15, 2023 at 05:24:27PM +0300, Alexey Dobriyan wrote:
> On Mon, Aug 14, 2023 at 11:37:51AM -0700, Andrew Morton wrote:

...

> > +__scanf(2, 3) int sscanf(const char *, const char *, ...);
> > +__scanf(2, 0) int vsscanf(const char *, const char *, va_list);
> 
> I'd suggest to leave scanf alone and rename file to printf.h
> Some archs have such files already (printf.c)

if you are talking about these

$ git ls-files */printf.c
arch/m68k/sun3/prom/printf.c
arch/sparc/prom/printf.c
arch/x86/boot/printf.c

they have no business with the main Linux kernel code.

I don't think we need to go that direction.

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2023-08-15 14:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-14 18:37 + lib-vsprintf-split-out-sprintf-and-friends.patch added to mm-nonmm-unstable branch Andrew Morton
2023-08-15 14:24 ` Alexey Dobriyan
2023-08-15 14:39   ` Andy Shevchenko [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=ZNuODCU2i0Mr2l8R@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dvyukov@google.com \
    --cc=elver@google.com \
    --cc=glider@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.