From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Petr Mladek <pmladek@suse.com>, Marco Elver <elver@google.com>,
linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com,
linux-mm@kvack.org
Cc: Steven Rostedt <rostedt@goodmis.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH v3 0/2] lib/vsprintf: Rework header inclusions
Date: Mon, 14 Aug 2023 19:33:42 +0300 [thread overview]
Message-ID: <20230814163344.17429-1-andriy.shevchenko@linux.intel.com> (raw)
Some patches that reduce the mess with the header inclusions related to
vsprintf.c module. Each patch has its own description, and has no
dependencies to each other, except the collisions over modifications
of the same places. Hence the series.
Changelog v3:
- dropped sorting headers patch (Petr)
- added tag (Marco)
Changelog v2:
- covered test_printf.c in patches 1 & 2
- do not remove likely implict inclusions (Rasmus)
- declare no_hash_pointers in sprintf.h (Marco, Steven, Rasmus)
Andy Shevchenko (2):
lib/vsprintf: Split out sprintf() and friends
lib/vsprintf: Declare no_hash_pointers in sprintf.h
include/linux/kernel.h | 30 +-----------------------------
include/linux/sprintf.h | 27 +++++++++++++++++++++++++++
lib/test_printf.c | 3 +--
lib/vsprintf.c | 1 +
mm/kfence/report.c | 3 +--
5 files changed, 31 insertions(+), 33 deletions(-)
create mode 100644 include/linux/sprintf.h
--
2.40.0.1.gaa8946217a0b
next reply other threads:[~2023-08-14 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 16:33 Andy Shevchenko [this message]
2023-08-14 16:33 ` [PATCH v3 1/2] lib/vsprintf: Split out sprintf() and friends Andy Shevchenko
2023-08-15 10:58 ` Petr Mladek
2023-08-14 16:33 ` [PATCH v3 2/2] lib/vsprintf: Declare no_hash_pointers in sprintf.h Andy Shevchenko
2023-08-15 10:58 ` Petr Mladek
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=20230814163344.17429-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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.