public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>
Cc: oberpar@linux.ibm.com, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Replace HTTP links with HTTPS ones: GCOV BASED KERNEL PROFILING
Date: Mon, 13 Jul 2020 11:29:52 -0600	[thread overview]
Message-ID: <20200713112952.762df60f@lwn.net> (raw)
In-Reply-To: <20200708161839.15170-1-grandmaster@al2klimov.de>

On Wed,  8 Jul 2020 18:18:39 +0200
"Alexander A. Klimov" <grandmaster@al2klimov.de> wrote:

>  Documentation/dev-tools/gcov.rst | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/dev-tools/gcov.rst b/Documentation/dev-tools/gcov.rst
> index 7bd013596217..9e989baae154 100644
> --- a/Documentation/dev-tools/gcov.rst
> +++ b/Documentation/dev-tools/gcov.rst
> @@ -22,7 +22,7 @@ Possible uses:
>  * minimizing kernel configurations (do I need this option if the
>    associated code is never run?)
>  
> -.. _gcov: http://gcc.gnu.org/onlinedocs/gcc/Gcov.html
> +.. _gcov: https://gcc.gnu.org/onlinedocs/gcc/Gcov.html
>  .. _lcov: http://ltp.sourceforge.net/coverage/lcov.php
>  
>  
> @@ -171,7 +171,7 @@ Note on compilers
>  GCC and LLVM gcov tools are not necessarily compatible. Use gcov_ to work with
>  GCC-generated .gcno and .gcda files, and use llvm-cov_ for Clang.
>  
> -.. _gcov: http://gcc.gnu.org/onlinedocs/gcc/Gcov.html
> +.. _gcov: https://gcc.gnu.org/onlinedocs/gcc/Gcov.html
>  .. _llvm-cov: https://llvm.org/docs/CommandGuide/llvm-cov.html

Applied, thanks.

jon

      reply	other threads:[~2020-07-13 17:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-08 16:18 [PATCH] Replace HTTP links with HTTPS ones: GCOV BASED KERNEL PROFILING Alexander A. Klimov
2020-07-13 17:29 ` Jonathan Corbet [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=20200713112952.762df60f@lwn.net \
    --to=corbet@lwn.net \
    --cc=grandmaster@al2klimov.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oberpar@linux.ibm.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