From: Mukesh Ojha <mojha@codeaurora.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
Jiri Kosina <trivial@kernel.org>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH trivial] crypto: Grammar s/options/option/, s/to/the/
Date: Wed, 20 Mar 2019 18:56:09 +0530 [thread overview]
Message-ID: <3333f63d-801c-d6c4-d6b1-5c871eee4282@codeaurora.org> (raw)
In-Reply-To: <20190320104103.21506-1-geert+renesas@glider.be>
On 3/20/2019 4:11 PM, Geert Uytterhoeven wrote:
> Fixes: ccb778e1841ce04b ("crypto: api - Add fips_enable flag")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> crypto/Kconfig | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/crypto/Kconfig b/crypto/Kconfig
> index bbab6bf3351982c9..14f3a98e32f78d06 100644
> --- a/crypto/Kconfig
> +++ b/crypto/Kconfig
> @@ -27,8 +27,8 @@ config CRYPTO_FIPS
> depends on (CRYPTO_ANSI_CPRNG || CRYPTO_DRBG) && !CRYPTO_MANAGER_DISABLE_TESTS
> depends on (MODULE_SIG || !MODULES)
> help
> - This options enables the fips boot option which is
> - required if you want to system to operate in a FIPS 200
> + This option enables the fips boot option which is
> + required if you want the system to operate in a FIPS 200
Reviewed-by: Mukesh Ojha <mojha@codeaurora.org>
Thanks,
Mukesh
> certification. You should say no unless you know what
> this is.
>
next prev parent reply other threads:[~2019-03-20 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 10:41 Geert Uytterhoeven
2019-03-20 13:26 ` Mukesh Ojha [this message]
2019-03-28 6:07 ` Herbert Xu
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=3333f63d-801c-d6c4-d6b1-5c871eee4282@codeaurora.org \
--to=mojha@codeaurora.org \
--cc=davem@davemloft.net \
--cc=geert+renesas@glider.be \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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
all inboxes | Powered by JetHome®