Linux Documentation
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: "Давыдов Иван Алексеевич" <davydoff33@yandex.ru>
Cc: linux-doc@vger.kernel.org, linux-kbuild@vger.kernel.org,
	corbet@lwn.net, masahiroy@kernel.org, nicolas@fjasle.eu
Subject: Re: [PATCH]: kbuild doc typo fix
Date: Sun, 21 Jul 2024 16:10:14 -0700	[thread overview]
Message-ID: <20240721231014.GA9588@thelio-3990X> (raw)
In-Reply-To: <1935A993-DAB0-4092-A1FE-B6501EE8E0DC@yandex.ru>

Hi Ivan,

First of all, thank you for noticing this and sending a patch!

I think the title of this commit could be improved a little bit. I think
using the prefix "kbuild: doc:" would be good, as that seems to be the
most common prefix I see when I look at 'git log --oneline' for this
file. This is not really a typo fix but more of a generalization because
clang is now a viable alternative to GCC, which could also be included
in commit message below. I suspect that was probably not the case when
this documentation was written.

On Sun, Jul 21, 2024 at 02:37:33PM +0300, Давыдов Иван Алексеевич wrote:
> In this part of the documentation, $(CC) is meant, but gcc is written.
> 
> Signed-off-by: Ivan Davydov <mailto:davydoff33@yandex.ru>

As for the patch itself, I cannot apply it directly from mutt or the
mailing list because it is quoted-printable:

  $ curl -LSs https://lore.kernel.org/all/1935A993-DAB0-4092-A1FE-B6501EE8E0DC@yandex.ru/raw | git apply -3v
  error: git diff header lacks filename information when removing 1 leading pathname component (line 63)

I suspect that is also why your signoff has a mailto: in it. Consider
looking at git-send-email or b4 send for sending your patches so that
your mail client does not mangle them in this way:

https://nickdesaulniers.github.io/blog/2017/05/16/submitting-your-first-patch-to-the-linux-kernel-and-responding-to-feedback/
https://b4.docs.kernel.org/en/latest/contributor/send.html

> ---
> diff --git a/Documentation/kbuild/makefiles.rst b/Documentation/kbuild/makefiles.rst
> index 991ce6081e35..be43990f1e7f 100644
> --- a/Documentation/kbuild/makefiles.rst
> +++ b/Documentation/kbuild/makefiles.rst
> @@ -578,7 +578,7 @@ cc-option
>    Note: cc-option uses KBUILD_CFLAGS for $(CC) options
>  
>  cc-option-yn
> -  cc-option-yn is used to check if gcc supports a given option
> +  cc-option-yn is used to check if $(CC) supports a given option
>    and return "y" if supported, otherwise "n".
>  
>    Example::
> @@ -596,7 +596,7 @@ cc-option-yn
>    Note: cc-option-yn uses KBUILD_CFLAGS for $(CC) options
>  
>  cc-disable-warning
> -  cc-disable-warning checks if gcc supports a given warning and returns
> +  cc-disable-warning checks if $(CC) supports a given warning and returns
>    the commandline switch to disable it. This special function is needed,
>    because gcc 4.4 and later accept any unknown -Wno-* option and only
>    warn about it if there is another warning in the source file.
> @@ -606,7 +606,7 @@ cc-disable-warning
>      KBUILD_CFLAGS += $(call cc-disable-warning, unused-but-set-variable)
>  
>    In the above example, -Wno-unused-but-set-variable will be added to
> -  KBUILD_CFLAGS only if gcc really accepts it.
> +  KBUILD_CFLAGS only if $(CC) really accepts it.
>  
>  gcc-min-version
>    gcc-min-version tests if the value of $(CONFIG_GCC_VERSION) is greater than

Other than the comments above, which are simple process things, this
change overall looks correct. Consider fixing those up and sending a v2
and I will be happy to provide a Reviewed-by tag.

Cheers,
Nathan

      reply	other threads:[~2024-07-21 23:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-21 11:37 [PATCH]: kbuild doc typo fix Давыдов Иван Алексеевич
2024-07-21 23:10 ` Nathan Chancellor [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=20240721231014.GA9588@thelio-3990X \
    --to=nathan@kernel.org \
    --cc=corbet@lwn.net \
    --cc=davydoff33@yandex.ru \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nicolas@fjasle.eu \
    /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