[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200731120426.6fa1b20d@oasis.local.home>
Date: Fri, 31 Jul 2020 12:04:26 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Andy Shevchenko <andy.shevchenko@...il.com>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Petr Mladek <pmladek@...e.com>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Rasmus Villemoes <linux@...musvillemoes.dk>
Subject: Re: [PATCH v1 3/3] lib/vsprintf: Force type of flags for gfp_t
On Fri, 31 Jul 2020 18:49:46 +0300
Andy Shevchenko <andy.shevchenko@...il.com> wrote:
> > > +++ b/lib/vsprintf.c
> > > @@ -1937,7 +1937,7 @@ char *flags_string(char *buf, char *end, void *flags_ptr,
> > > names = vmaflag_names;
> > > break;
> > > case 'g':
> > > - flags = *(gfp_t *)flags_ptr;
> > > + flags = (__force typeof(flags))(*(gfp_t *)flags_ptr);
> >
> > Do we really need to say "typeof(flags)" ? What about simply using
> > flags' type?
>
> Whatever you prefer. I actually came with the latter and switched to the former.
> So, I'll switch back for v2.
For this instance, I prefer spelling out the type.
Thanks!
-- Steve
Powered by blists - more mailing lists