All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, dvyukov@google.com,
	bagasdotme@gmail.com, andreyknvl@google.com,
	akpm@linux-foundation.org
Subject: [folded-merged] kcov-improve-documentation-v3.patch removed from -mm tree
Date: Wed, 05 Apr 2023 19:49:18 -0700	[thread overview]
Message-ID: <20230406024919.0293BC433D2@smtp.kernel.org> (raw)


The quilt patch titled
     Subject: kcov-improve-documentation-v3
has been removed from the -mm tree.  Its filename was
     kcov-improve-documentation-v3.patch

This patch was dropped because it was folded into kcov-improve-documentation.patch

------------------------------------------------------
From: Andrey Konovalov <andreyknvl@google.com>
Subject: kcov-improve-documentation-v3
Date: Wed, 1 Mar 2023 16:36:09 +0100

fix ``annotation`` for KCOV_REMOTE_ENABLE

Link: https://lkml.kernel.org/r/72be5c215c275f35891229b90622ed859f196a46.1677684837.git.andreyknvl@google.com
Signed-off-by: Andrey Konovalov <andreyknvl@google.com>
Reviewed-by: Dmitry Vyukov <dvyukov@google.com>
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 Documentation/dev-tools/kcov.rst |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/Documentation/dev-tools/kcov.rst~kcov-improve-documentation-v3
+++ a/Documentation/dev-tools/kcov.rst
@@ -229,7 +229,7 @@ Using KCOV to collect remote coverage re
 1. Modifying kernel code to annotate the code section from where coverage
    should be collected with ``kcov_remote_start`` and ``kcov_remote_stop``.
 
-2. Using `KCOV_REMOTE_ENABLE`` instead of ``KCOV_ENABLE`` in the userspace
+2. Using ``KCOV_REMOTE_ENABLE`` instead of ``KCOV_ENABLE`` in the userspace
    process that collects coverage.
 
 Both ``kcov_remote_start`` and ``kcov_remote_stop`` annotations and the
_

Patches currently in -mm which might be from andreyknvl@google.com are

kcov-improve-documentation.patch


                 reply	other threads:[~2023-04-06  2:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230406024919.0293BC433D2@smtp.kernel.org \
    --to=akpm@linux-foundation.org \
    --cc=andreyknvl@google.com \
    --cc=bagasdotme@gmail.com \
    --cc=dvyukov@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.