From: David Miller <davem@davemloft.net>
To: keescook@chromium.org
Cc: joe@perches.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: ethtool: Fix comment mentioning typo in IS_ENABLED()
Date: Fri, 05 Jun 2020 13:17:16 -0700 (PDT) [thread overview]
Message-ID: <20200605.131716.1384746623877149157.davem@davemloft.net> (raw)
In-Reply-To: <202006050720.D741B4C@keescook>
From: Kees Cook <keescook@chromium.org>
Date: Fri, 5 Jun 2020 07:21:22 -0700
> This has no code changes, but it's a typo noticed in other clean-ups,
> so we might as well fix it. IS_ENABLED() takes full names, and should
> have the "CONFIG_" prefix.
>
> Reported-by: Joe Perches <joe@perches.com>
> Link: https://lore.kernel.org/lkml/b08611018fdb6d88757c6008a5c02fa0e07b32fb.camel@perches.com
> Signed-off-by: Kees Cook <keescook@chromium.org>
Applied, thank you.
prev parent reply other threads:[~2020-06-05 20:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 14:21 [PATCH] net: ethtool: Fix comment mentioning typo in IS_ENABLED() Kees Cook
2020-06-05 20:17 ` David Miller [this message]
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=20200605.131716.1384746623877149157.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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).