From: Sean Christopherson <seanjc@google.com>
To: Luiz Capitulino <luizcap@amazon.com>
Cc: stable@vger.kernel.org, christophe.jaillet@wanadoo.fr,
lcapitulino@gmail.com
Subject: Re: [PATH 6.1.y 1/2] KVM: x86/mmu: Use kstrtobool() instead of strtobool()
Date: Tue, 5 Sep 2023 17:01:39 -0700 [thread overview]
Message-ID: <ZPfBY5rnDwEIDR90@google.com> (raw)
In-Reply-To: <8c1fdd1cb24d042d02c4f2660c0690604448a2f4.1693593288.git.luizcap@amazon.com>
On Fri, Sep 01, 2023, Luiz Capitulino wrote:
> From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
>
> Commit 11b36fe7d4500c8ef73677c087f302fd713101c2 upstream.
>
> 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>
> Link: https://lore.kernel.org/r/670882aa04dbdd171b46d3b20ffab87158454616.1673689135.git.christophe.jaillet@wanadoo.fr
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> Signed-off-by: Luiz Capitulino <luizcap@amazon.com>
> ---
Acked-by: Sean Christopherson <seanjc@google.com>
next prev parent reply other threads:[~2023-09-06 0:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 18:34 [PATH 6.1.y 0/2] Backport KVM's nx_huge_pages=never module parameter Luiz Capitulino
2023-09-01 18:34 ` [PATH 6.1.y 1/2] KVM: x86/mmu: Use kstrtobool() instead of strtobool() Luiz Capitulino
2023-09-06 0:01 ` Sean Christopherson [this message]
2023-09-01 18:34 ` [PATH 6.1.y 2/2] KVM: x86/mmu: Add "never" option to allow sticky disabling of nx_huge_pages Luiz Capitulino
2023-09-06 0:02 ` Sean Christopherson
2023-09-02 7:27 ` [PATH 6.1.y 0/2] Backport KVM's nx_huge_pages=never module parameter Greg KH
2023-09-03 17:28 ` Luiz Capitulino
2023-09-07 11:25 ` Greg KH
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=ZPfBY5rnDwEIDR90@google.com \
--to=seanjc@google.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=lcapitulino@gmail.com \
--cc=luizcap@amazon.com \
--cc=stable@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).