From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: <pmladek@suse.com>, <rostedt@goodmis.org>,
<sergey.senozhatsky@gmail.com>, <shuah@kernel.org>
Cc: <patches@opensource.cirrus.com>, <linux-kernel@vger.kernel.org>,
<linux-kselftest@vger.kernel.org>,
Richard Fitzgerald <rf@opensource.cirrus.com>
Subject: [PATCH v2 4/4] MAINTAINERS: Add lib/test_scanf.c to VSPRINTF
Date: Mon, 30 Nov 2020 14:58:00 +0000 [thread overview]
Message-ID: <20201130145800.19960-4-rf@opensource.cirrus.com> (raw)
In-Reply-To: <20201130145800.19960-1-rf@opensource.cirrus.com>
Adds the new scanf test to the VSPRINTF group.
Signed-off-by: Richard Fitzgerald <rf@opensource.cirrus.com>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 7887d2161be4..d2bf38bd3d0c 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -18782,6 +18782,7 @@ S: Maintained
T: git git://git.kernel.org/pub/scm/linux/kernel/git/pmladek/printk.git
F: Documentation/core-api/printk-formats.rst
F: lib/test_printf.c
+F: lib/test_scanf.c
F: lib/vsprintf.c
VT1211 HARDWARE MONITOR DRIVER
--
2.20.1
next prev parent reply other threads:[~2020-11-30 14:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 14:57 [PATCH v2 1/4] lib: vsprintf: Fix handling of number field widths in vsscanf Richard Fitzgerald
2020-11-30 14:57 ` [PATCH v2 2/4] lib: test_scanf: Add tests for sscanf number conversion Richard Fitzgerald
2020-12-09 14:15 ` Petr Mladek
2020-12-15 14:26 ` Richard Fitzgerald
2020-12-16 15:00 ` Petr Mladek
2020-11-30 14:57 ` [PATCH v2 3/4] selftests: lib: Add wrapper script for test_scanf Richard Fitzgerald
2020-12-09 14:20 ` Petr Mladek
2020-11-30 14:58 ` Richard Fitzgerald [this message]
2020-12-09 14:22 ` [PATCH v2 4/4] MAINTAINERS: Add lib/test_scanf.c to VSPRINTF Petr Mladek
2020-12-15 18:45 ` Shuah Khan
2020-12-08 16:59 ` [PATCH v2 1/4] lib: vsprintf: Fix handling of number field widths in vsscanf pmladek
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=20201130145800.19960-4-rf@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=shuah@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;
as well as URLs for NNTP newsgroup(s).