All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,mario.limonciello@amd.com,akpm@linux-foundation.org
Subject: [merged mm-nonmm-stable] kstrtox-add-support-for-enabled-and-disabled-in-kstrtobool.patch removed from -mm tree
Date: Sun, 11 May 2025 17:55:50 -0700	[thread overview]
Message-ID: <20250512005551.79586C4CEE4@smtp.kernel.org> (raw)


The quilt patch titled
     Subject: kstrtox: add support for enabled and disabled in kstrtobool()
has been removed from the -mm tree.  Its filename was
     kstrtox-add-support-for-enabled-and-disabled-in-kstrtobool.patch

This patch was dropped because it was merged into the mm-nonmm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

------------------------------------------------------
From: Mario Limonciello <mario.limonciello@amd.com>
Subject: kstrtox: add support for enabled and disabled in kstrtobool()
Date: Thu, 20 Mar 2025 21:25:01 -0500

In some places in the kernel there is a design pattern for sysfs
attributes to use kstrtobool() in store() and str_enabled_disabled() in
show().

This is counterintuitive to interact with because kstrtobool() takes
on/off but str_enabled_disabled() shows enabled/disabled.  Some of those
sysfs uses could switch to str_on_off() but for some attributes
enabled/disabled really makes more sense.

Add support for kstrtobool() to accept enabled/disabled.

Link: https://lkml.kernel.org/r/20250321022538.1532445-1-superm1@kernel.org
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 lib/kstrtox.c |    4 ++++
 1 file changed, 4 insertions(+)

--- a/lib/kstrtox.c~kstrtox-add-support-for-enabled-and-disabled-in-kstrtobool
+++ a/lib/kstrtox.c
@@ -351,6 +351,8 @@ int kstrtobool(const char *s, bool *res)
 		return -EINVAL;
 
 	switch (s[0]) {
+	case 'e':
+	case 'E':
 	case 'y':
 	case 'Y':
 	case 't':
@@ -358,6 +360,8 @@ int kstrtobool(const char *s, bool *res)
 	case '1':
 		*res = true;
 		return 0;
+	case 'd':
+	case 'D':
 	case 'n':
 	case 'N':
 	case 'f':
_

Patches currently in -mm which might be from mario.limonciello@amd.com are



                 reply	other threads:[~2025-05-12  0:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20250512005551.79586C4CEE4@smtp.kernel.org \
    --to=akpm@linux-foundation.org \
    --cc=mario.limonciello@amd.com \
    --cc=mm-commits@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.