From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Rodrigo Alencar <455.rodrigo.alencar@gmail.com>
Cc: Petr Mladek <pmladek@suse.com>,
Dmitry Antipov <dmantipov@yandex.ru>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
rodrigo.alencar@analog.com, dlechner@baylibre.com,
jic23@kernel.org
Subject: Re: [PATCH v1 0/2] kstrtox: make _parse_integer() flexible
Date: Wed, 3 Jun 2026 16:58:40 +0300 [thread overview]
Message-ID: <aiAzEMuV3K08hjtK@ashevche-desk.local> (raw)
In-Reply-To: <p5atlsrh3srkdfnvujdota2dq7x5oadz76yauytwwm7bozvst6@mzubvy5vg45s>
On Wed, Jun 03, 2026 at 01:10:11PM +0100, Rodrigo Alencar wrote:
> On 26/06/03 12:51PM, Rodrigo Alencar wrote:
> > On 26/06/03 01:23PM, Petr Mladek wrote:
...
> Actually the example pattern with static inline is not this one, it is
> under linux/reset.h with __devm_reset_control_get().
>
> If every one agrees I can add that to the v16 of the patch series
> of the PLL driver.
...which shows disadvantage of the naming (it grows quite rapidly towards the nonsense,
like devm_reset_control_array_get_exclusive_released().
Again, that's public API and I see at least some value in that. In more closed
one as we discuss in this thread that adds no value.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-06-03 13:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 20:29 Andy Shevchenko
2026-06-02 20:29 ` [PATCH v1 1/2] kstrtox: Make _parse_integer() take variadic arguments Andy Shevchenko
2026-06-03 6:47 ` Andy Shevchenko
2026-06-03 10:37 ` David Laight
2026-06-03 10:54 ` Andy Shevchenko
2026-06-03 10:56 ` Andy Shevchenko
2026-06-03 11:34 ` David Laight
2026-06-02 20:29 ` [PATCH v1 2/2] vsprintf: Convert to use _parse_integer() instead of _parse_integer_limit() Andy Shevchenko
2026-06-03 11:23 ` [PATCH v1 0/2] kstrtox: make _parse_integer() flexible Petr Mladek
2026-06-03 11:51 ` Rodrigo Alencar
2026-06-03 12:10 ` Rodrigo Alencar
2026-06-03 13:58 ` Andy Shevchenko [this message]
2026-06-03 13:53 ` Andy Shevchenko
2026-06-04 6:59 ` Petr Mladek
2026-06-04 7:19 ` Andy Shevchenko
2026-06-04 7:48 ` Rodrigo Alencar
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=aiAzEMuV3K08hjtK@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=455.rodrigo.alencar@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dlechner@baylibre.com \
--cc=dmantipov@yandex.ru \
--cc=jic23@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pmladek@suse.com \
--cc=rodrigo.alencar@analog.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.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
all inboxes | Powered by JetHome®