From: Petr Mladek <pmladek@suse.com>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: rostedt@goodmis.org, sergey.senozhatsky@gmail.com,
andriy.shevchenko@linux.intel.com, linux@rasmusvillemoes.dk,
w@1wt.eu, lkml@sdf.org, davem@davemloft.net, kuba@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH 0/2] Fix truncation warnings from building test_scanf.c
Date: Thu, 27 May 2021 16:10:23 +0200 [thread overview]
Message-ID: <YK+oT02rkFOujT3C@alley> (raw)
In-Reply-To: <YKzBbB/QIJrgPrmq@alley>
On Tue 2021-05-25 11:20:45, Petr Mladek wrote:
> On Mon 2021-05-24 16:59:39, Richard Fitzgerald wrote:
> > The kernel test robot is reporting truncation warnings when building
> > lib/test_scanf.c:
> >
> > Richard Fitzgerald (2):
> > lib: test_scanf: Fix incorrect use of type_min() with unsigned types
> > random32: Fix implicit truncation warning in prandom_seed_state()
> >
> > include/linux/prandom.h | 2 +-
> > lib/test_scanf.c | 13 ++++++-------
> > 2 files changed, 7 insertions(+), 8 deletions(-)
>
> For both patches:
>
> Reviewed-by: Petr Mladek <pmladek@suse.com>
>
> I am going to commit them within next two days or so unless anyone
> complains in the meantime.
JFYI, both patches have been committed into printk/linux.git,
branch for-5.14-vsprintf-scanf.
Best Regards,
Petr
prev parent reply other threads:[~2021-05-27 14:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 15:59 [PATCH 0/2] Fix truncation warnings from building test_scanf.c Richard Fitzgerald
2021-05-24 15:59 ` [PATCH 1/2] lib: test_scanf: Fix incorrect use of type_min() with unsigned types Richard Fitzgerald
2021-05-25 9:55 ` Rasmus Villemoes
2021-05-25 10:10 ` Richard Fitzgerald
2021-05-25 10:30 ` Rasmus Villemoes
2021-05-27 21:59 ` Luc Van Oostenryck
2021-05-24 15:59 ` [PATCH 2/2] random32: Fix implicit truncation warning in prandom_seed_state() Richard Fitzgerald
2021-05-25 9:20 ` [PATCH 0/2] Fix truncation warnings from building test_scanf.c Petr Mladek
2021-05-27 14:10 ` 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=YK+oT02rkFOujT3C@alley \
--to=pmladek@suse.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=lkml@sdf.org \
--cc=netdev@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=rf@opensource.cirrus.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=w@1wt.eu \
/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).