From: Randy Dunlap <rdunlap@infradead.org>
To: Julian Braha <julianbraha@gmail.com>, nathan@kernel.org, nsc@kernel.org
Cc: vegard.nossum@oracle.com, kees@kernel.org,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kconfig: fix minor typos in comments
Date: Sun, 19 Jul 2026 14:56:32 -0700 [thread overview]
Message-ID: <b97d71f8-bd98-48c5-be05-c9f4f4b0a994@infradead.org> (raw)
In-Reply-To: <20260719210536.9577-1-julianbraha@gmail.com>
On 7/19/26 2:05 PM, Julian Braha wrote:
> Some typos I noticed:
> 1. expressoin -> expression
> 2. A property represent -> A property represents
>
> Signed-off-by: Julian Braha <julianbraha@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> scripts/kconfig/expr.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/kconfig/expr.h b/scripts/kconfig/expr.h
> index 5f900d18dae0..fa3823a97d72 100644
> --- a/scripts/kconfig/expr.h
> +++ b/scripts/kconfig/expr.h
> @@ -38,7 +38,7 @@ union expr_data {
> * struct expr - expression
> *
> * @node: link node for the hash table
> - * @type: expressoin type
> + * @type: expression type
> * @val: calculated tristate value
> * @val_is_valid: indicate whether the value is valid
> * @left: left node
> @@ -160,7 +160,7 @@ struct symbol {
>
> #define SYMBOL_MAXLENGTH 256
>
> -/* A property represent the config options that can be associated
> +/* A property represents the config options that can be associated
> * with a config "symbol".
> * Sample:
> * config FOO
--
~Randy
next prev parent reply other threads:[~2026-07-19 21:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-19 21:05 Julian Braha
2026-07-19 21:56 ` Randy Dunlap [this message]
2026-07-21 10:52 ` Nicolas Schier
2026-07-23 23:18 ` Nathan Chancellor
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=b97d71f8-bd98-48c5-be05-c9f4f4b0a994@infradead.org \
--to=rdunlap@infradead.org \
--cc=julianbraha@gmail.com \
--cc=kees@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=vegard.nossum@oracle.com \
/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®