From: Jonathan Cameron <jic23@kernel.org>
To: Rodrigo Alencar <455.rodrigo.alencar@gmail.com>
Cc: rodrigo.alencar@analog.com, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, linux@analog.com,
David Lechner <dlechner@baylibre.com>,
Andy Shevchenko <andy@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v16 04/14] lib: kstrtox: add initial value to _parse_integer_limit()
Date: Wed, 24 Jun 2026 15:54:14 +0100 [thread overview]
Message-ID: <20260624155414.61755e9a@jic23-huawei> (raw)
In-Reply-To: <20260614210044.19dfc8df@jic23-huawei>
On Sun, 14 Jun 2026 21:00:44 +0100
Jonathan Cameron <jic23@kernel.org> wrote:
> On Thu, 4 Jun 2026 11:09:33 +0100
> Rodrigo Alencar <455.rodrigo.alencar@gmail.com> wrote:
>
> > On 26/06/04 10:58AM, Rodrigo Alencar via B4 Relay wrote:
> > > From: Rodrigo Alencar <rodrigo.alencar@analog.com>
> > >
> > > Add init parameter to _parse_integer_limit() that defines an initial
> > > value for the accumulated result when parsing an 64-bit integer. The
> > > new function prototype is adjusted so that the _parse_integer() macros
> > > stay consistent allowing for one more argument, which defaults to 0.
> >
> > ...
> >
> > > noinline
> > > unsigned int _parse_integer_limit(const char *s, unsigned int base, unsigned long long *p,
> > > - size_t max_chars)
> > > + size_t max_chars, unsigned long long init)
> > > {
> > > unsigned long long res;
> > > unsigned int rv;
> > >
> > > - res = 0;
> > > + res = init;
> >
> > This might generate conflict, as the code around have changed in linux-next.
> > It is an easy fix though.
> >
> Thanks for the heads up. Hopefully that will all fall out when I rebase testing
> on rc1 once that is out.
I've done a mid merge cycle rebase as the char-misc branches have merged.
So this should be resolve on my testing branch now.
Thanks
Jonathan
>
> Jonathan
>
> > > rv = 0;
> > > while (max_chars--) {
> > > unsigned int c = *s;
> >
>
>
next prev parent reply other threads:[~2026-06-24 14:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 9:58 [PATCH v16 00/14] ADF41513/ADF41510 PLL frequency synthesizers Rodrigo Alencar via B4 Relay
2026-06-04 9:58 ` [PATCH v16 01/14] dt-bindings: iio: frequency: add adf41513 Rodrigo Alencar via B4 Relay
2026-06-04 9:58 ` [PATCH v16 02/14] lib: kstrtox: Make _parse_integer() take variadic arguments Rodrigo Alencar via B4 Relay
2026-06-04 9:58 ` [PATCH v16 03/14] lib: vsprintf: use _parse_integer() instead of _parse_integer_limit() Rodrigo Alencar via B4 Relay
2026-06-04 10:06 ` Rodrigo Alencar
2026-06-04 19:34 ` Andy Shevchenko
2026-06-04 9:58 ` [PATCH v16 04/14] lib: kstrtox: add initial value to _parse_integer_limit() Rodrigo Alencar via B4 Relay
2026-06-04 10:09 ` Rodrigo Alencar
2026-06-14 20:00 ` Jonathan Cameron
2026-06-24 14:54 ` Jonathan Cameron [this message]
2026-06-25 7:30 ` Rodrigo Alencar
2026-06-04 19:31 ` Andy Shevchenko
2026-06-04 9:58 ` [PATCH v16 05/14] lib: kstrtox: add kstrtoudec64() and kstrtodec64() Rodrigo Alencar via B4 Relay
2026-06-04 19:40 ` Andy Shevchenko
2026-06-04 9:59 ` [PATCH v16 06/14] lib: test-kstrtox: tests for kstrtodec64() and kstrtoudec64() Rodrigo Alencar via B4 Relay
2026-06-04 9:59 ` [PATCH v16 07/14] lib: math: div64: add div64_s64_rem() Rodrigo Alencar via B4 Relay
2026-06-04 9:59 ` [PATCH v16 08/14] iio: core: add decimal value formatting into 64-bit value Rodrigo Alencar via B4 Relay
2026-06-08 20:32 ` Nuno Sá
2026-06-04 9:59 ` [PATCH v16 09/14] iio: test: iio-test-format: add test case for decimal format Rodrigo Alencar via B4 Relay
2026-06-04 19:45 ` Andy Shevchenko
2026-06-04 9:59 ` [PATCH v16 10/14] iio: frequency: adf41513: driver implementation Rodrigo Alencar via B4 Relay
2026-06-04 9:59 ` [PATCH v16 11/14] iio: frequency: adf41513: handle LE synchronization feature Rodrigo Alencar via B4 Relay
2026-06-04 9:59 ` [PATCH v16 12/14] iio: frequency: adf41513: features on frequency change Rodrigo Alencar via B4 Relay
2026-06-04 9:59 ` [PATCH v16 13/14] docs: iio: add documentation for adf41513 driver Rodrigo Alencar via B4 Relay
2026-06-04 9:59 ` [PATCH v16 14/14] Documentation: ABI: testing: add common ABI file for iio/frequency Rodrigo Alencar via B4 Relay
2026-06-14 20:56 ` [PATCH v16 00/14] ADF41513/ADF41510 PLL frequency synthesizers Jonathan Cameron
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=20260624155414.61755e9a@jic23-huawei \
--to=jic23@kernel.org \
--cc=455.rodrigo.alencar@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@analog.com \
--cc=linux@rasmusvillemoes.dk \
--cc=pmladek@suse.com \
--cc=robh@kernel.org \
--cc=rodrigo.alencar@analog.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=skhan@linuxfoundation.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