[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <98acdfce0da0d7c3b33571528064935c107cbbc5.camel@perches.com>
Date: Thu, 01 Aug 2019 12:58:08 -0700
From: Joe Perches <joe@...ches.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Miguel Ojeda Sandonis <miguel.ojeda.sandonis@...il.com>,
linux-kernel@...r.kernel.org,
Geert Uytterhoeven <geert+renesas@...der.be>,
Mans Rullgard <mans@...sr.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Petr Mladek <pmladek@...e.com>
Subject: Re: [PATCH v4 1/2] kernel.h: Update comment about
simple_strto<foo>() functions
On Thu, 2019-08-01 at 22:29 +0300, Andy Shevchenko wrote:
> There were discussions in the past about use cases for
> simple_strto<foo>() functions and, in some rare cases,
> they have a benefit over kstrto<foo>() ones.
[]
> diff --git a/include/linux/kernel.h b/include/linux/kernel.h
[]
> @@ -334,8 +334,7 @@ int __must_check kstrtoll(const char *s, unsigned int base, long long *res);
> * @res: Where to write the result of the conversion on success.
> *
> * Returns 0 on success, -ERANGE on overflow and -EINVAL on parsing error.
> - * Used as a replacement for the obsolete simple_strtoull. Return code must
> - * be checked.
> + * Used as a replacement for the simple_strtoull. Return code must be checked.
Using 'the' here is unnecessary and somewhat confusing.
Perhaps:
* Preferred over simple_strtoull() unless the end position is required
* Return value must be checked
>
Powered by blists - more mailing lists