From: Petr Mladek <pmladek@suse.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>
Cc: "Rasmus Villemoes" <linux@rasmusvillemoes.dk>,
"Sergey Senozhatsky" <sergey.senozhatsky.work@gmail.com>,
linux-kernel@vger.kernel.org,
"Uwe Kleine-König" <uwe@kleine-koenig.org>,
"Ilya Dryomov" <idryomov@gmail.com>,
"Kees Cook" <keescook@chromium.org>,
"Tobin C . Harding" <me@tobin.cc>,
"Petr Mladek" <pmladek@suse.com>
Subject: [PATCH 0/3] lib/test_printf: Clean up basic pointer testing
Date: Thu, 27 Feb 2020 14:01:20 +0100 [thread overview]
Message-ID: <20200227130123.32442-1-pmladek@suse.com> (raw)
The discussion about hashing NULL pointer value[1] uncovered that
the basic tests of pointer formatting do not follow the original
structure and cause confusion.
I feel responsible for it and here is a proposed clean up.
[1] https://lkml.kernel.org/r/bcfb2f94-e7a8-0860-86e3-9fc866d98742@rasmusvillemoes.dk
Petr Mladek (3):
lib/test_printf: Clean up test of hashed pointers
lib/test_printf: Fix structure of basic pointer tests
lib/test_printf: Clean up invalid pointer value testing
lib/test_printf.c | 170 ++++++++++++++++++++----------------------------------
1 file changed, 64 insertions(+), 106 deletions(-)
--
2.16.4
next reply other threads:[~2020-02-27 13:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 13:01 Petr Mladek [this message]
2020-02-27 13:01 ` [PATCH 1/3] lib/test_printf: Clean up test of hashed pointers Petr Mladek
2020-02-27 14:30 ` Uwe Kleine-König
2020-03-02 10:24 ` Petr Mladek
2020-03-03 11:14 ` Rasmus Villemoes
2020-02-27 13:01 ` [PATCH 2/3] lib/test_printf: Fix structure of basic pointer tests Petr Mladek
2020-02-27 13:01 ` [PATCH 3/3] lib/test_printf: Clean up invalid pointer value testing Petr Mladek
2020-03-03 7:24 ` [PATCH 0/3] lib/test_printf: Clean up basic pointer testing Sergey Senozhatsky
2020-03-03 9:22 ` Petr Mladek
2020-03-03 10:32 ` Sergey Senozhatsky
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=20200227130123.32442-1-pmladek@suse.com \
--to=pmladek@suse.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=idryomov@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=me@tobin.cc \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@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 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.