linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-input@vger.kernel.org
Subject: Re: [PATCH 12/30] input: Use kstrtobool() instead of strtobool()
Date: Thu, 3 Nov 2022 22:37:19 +0100	[thread overview]
Message-ID: <a0a59528-6af4-adb2-e4e2-cb4cbe15e986@wanadoo.fr> (raw)
In-Reply-To: <Y2Qowvjn+7jT767t@google.com>

Le 03/11/2022 à 21:46, Dmitry Torokhov a écrit :
> On Tue, Nov 01, 2022 at 10:14:00PM +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: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> 
> Please feel free to merge with the rest of the series. Or let me know if
> you want me to pick just this one through my tree.
> 
> Thanks.
> 

Hi,

the patch can go through your tree.
There is no plan to merge the whole serie at once, and some other 
maintainers have asked for some patches to be re-sent as individual patches.

CJ

  reply	other threads:[~2022-11-03 21:37 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01 21:05 [PATCH 00/30] Remove strtobool() Christophe JAILLET
2022-11-01 21:13 ` [PATCH 01/30] net: usb: Use kstrtobool() instead of strtobool() Christophe JAILLET
2022-11-02  3:27   ` Jakub Kicinski
2022-11-01 21:13 ` [PATCH 02/30] wifi: " Christophe JAILLET
2022-11-08  7:39   ` Kalle Valo
2022-11-01 21:13 ` [PATCH 03/30] irqchip: " Christophe JAILLET
2022-11-26 12:46   ` Marc Zyngier
2022-11-26 15:16     ` Christophe JAILLET
2022-11-01 21:13 ` [PATCH 04/30] scsi: target: " Christophe JAILLET
2022-11-02  5:54   ` Chaitanya Kulkarni
2022-11-08  3:54   ` Martin K. Petersen
2022-11-17 18:29   ` Martin K. Petersen
2022-11-01 21:13 ` [PATCH 05/30] nvdimm: " Christophe JAILLET
2022-11-01 21:13 ` [PATCH 06/30] nvme: " Christophe JAILLET
2022-11-02  5:52   ` Chaitanya Kulkarni
2022-11-02  6:47   ` Christoph Hellwig
2022-11-02  6:57     ` Christophe JAILLET
2022-11-02  6:58       ` Christoph Hellwig
2022-11-02  7:05       ` Julia Lawall
2022-11-01 21:13 ` [PATCH 07/30] usb: core: " Christophe JAILLET
2022-11-01 21:13 ` [PATCH 08/30] usb: gadget: " Christophe JAILLET
2022-11-01 21:13 ` [PATCH 09/30] ACPI: sysfs: " Christophe JAILLET
2022-11-02 11:33   ` Andy Shevchenko
2022-11-03 18:48     ` Rafael J. Wysocki
2022-11-01 21:13 ` [PATCH 10/30] clocksource/drivers/arm_arch_timer: " Christophe JAILLET
2022-11-02 10:56   ` Mark Rutland
2022-12-02 12:17   ` Daniel Lezcano
2022-11-01 21:13 ` [PATCH 11/30] greybus: svc: " Christophe JAILLET
2022-11-01 21:49   ` Alex Elder
2022-11-02  7:31   ` Johan Hovold
2022-11-01 21:14 ` [PATCH 12/30] input: " Christophe JAILLET
2022-11-03 20:46   ` Dmitry Torokhov
2022-11-03 21:37     ` Christophe JAILLET [this message]
2022-11-07 19:40       ` Dmitry Torokhov
2022-11-01 21:14 ` [PATCH 13/30] platform/chrome: " Christophe JAILLET
2022-11-02  4:30   ` patchwork-bot+chrome-platform
2022-11-02 12:30   ` patchwork-bot+chrome-platform
2022-11-01 21:14 ` [PATCH 14/30] powercap: " Christophe JAILLET
2022-11-03 18:39   ` Rafael J. Wysocki
2022-11-01 21:14 ` [PATCH 15/30] video: fbdev: omapfb: " Christophe JAILLET
2022-11-01 21:14 ` [PATCH 16/30] cifs: " Christophe JAILLET
2022-11-01 21:14 ` [PATCH 17/30] initramfs: " Christophe JAILLET
2022-11-01 21:14 ` [PATCH 18/30] module: " Christophe JAILLET
2022-11-02 18:41   ` Luis Chamberlain
2023-01-14 13:32     ` Christophe JAILLET
2022-11-06 15:03   ` Aaron Tomlin
2023-01-17 15:39   ` Luis Chamberlain
2022-11-01 21:14 ` [PATCH 19/30] kernel/params.c: " Christophe JAILLET
2022-11-01 21:14 ` [PATCH 20/30] mm/damon: " Christophe JAILLET
2022-11-01 22:00   ` SeongJae Park
2022-11-01 21:14 ` [PATCH 21/30] mm: " Christophe JAILLET
2022-11-01 22:47   ` Kees Cook
2022-11-02 11:29     ` Andy Shevchenko
2022-11-05  2:58   ` Pasha Tatashin
2022-11-01 21:14 ` [PATCH 22/30] Bluetooth: hci_debugfs: " Christophe JAILLET
2022-11-01 21:14 ` [PATCH 23/30] test_firmware: " Christophe JAILLET
2022-11-01 21:14 ` [PATCH 24/30] arm64: cpufeature: " Christophe JAILLET
2022-11-02 13:46   ` Catalin Marinas
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
2022-11-01 21:14 ` [PATCH 26/30] s390/ipl: " Christophe JAILLET
2022-11-08 14:53   ` Alexander Gordeev
2022-11-01 21:14 ` [PATCH 27/30] KVM: x86/mmu: " Christophe JAILLET
2022-11-01 21:14 ` [PATCH 28/30] x86/xen: " Christophe JAILLET
2022-11-01 23:11   ` Boris Ostrovsky
2022-11-01 21:14 ` [PATCH 29/30] driver core: " Christophe JAILLET
2022-11-01 21:14 ` [PATCH 30/30] kstrtox: Remove strtobool() Christophe JAILLET
2022-11-01 21:18   ` Christophe JAILLET
2022-11-02 11:18 ` [PATCH 00/30] " Andy Shevchenko
2023-01-20 18:18 ` (subset) " 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=a0a59528-6af4-adb2-e4e2-cb4cbe15e986@wanadoo.fr \
    --to=christophe.jaillet@wanadoo.fr \
    --cc=dmitry.torokhov@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.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).