From: Catalin Marinas <catalin.marinas@arm.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 24/30] arm64: cpufeature: Use kstrtobool() instead of strtobool()
Date: Wed, 2 Nov 2022 13:46:44 +0000 [thread overview]
Message-ID: <Y2J0xJ61iclx6WZG@arm.com> (raw)
In-Reply-To: <5a1b329cda34aec67615c0d2fd326eb0d6634bf7.1667336095.git.christophe.jaillet@wanadoo.fr>
On Tue, Nov 01, 2022 at 10:14:12PM +0100, Christophe JAILLET wrote:
> strtobool() is the same as kstrtobool().
> However, the latter is more used within the kernel.
>
> In order to remove strtobool() and slightly simplify kstrtox.h, switch to
> the other function name.
>
> While at it, include the corresponding header file (<linux/kstrtox.h>)
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-11-02 13:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1667336095.git.christophe.jaillet@wanadoo.fr>
2022-11-01 21:13 ` [PATCH 10/30] clocksource/drivers/arm_arch_timer: Use kstrtobool() instead of strtobool() Christophe JAILLET
2022-11-02 10:56 ` Mark Rutland
2022-12-02 12:17 ` Daniel Lezcano
2022-11-01 21:14 ` [PATCH 24/30] arm64: cpufeature: " Christophe JAILLET
2022-11-02 13:46 ` Catalin Marinas [this message]
2023-01-14 13:29 ` Christophe JAILLET
2023-01-16 18:40 ` Catalin Marinas
2022-11-01 21:14 ` [PATCH 25/30] KVM: arm64: vgic-v3: " Christophe JAILLET
2023-01-20 18:18 ` (subset) [PATCH 00/30] Remove strtobool() Catalin Marinas
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=Y2J0xJ61iclx6WZG@arm.com \
--to=catalin.marinas@arm.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).