From: Dmitry Vyukov <dvyukov@google.com>
To: tl455047 <tl445047925@gmail.com>
Cc: kasan-dev <kasan-dev@googlegroups.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux-MM <linux-mm@kvack.org>
Subject: Re: [PATCH] kernel: kcov: fix a typo in comment
Date: Tue, 23 Mar 2021 07:45:36 +0100 [thread overview]
Message-ID: <CACT4Y+atQZKKQqdUrk-JvQNXaZCBHz0S_tSkFuOA+nkTS4eoHg@mail.gmail.com> (raw)
In-Reply-To: <20210323062303.19541-1-tl445047925@gmail.com>
On Tue, Mar 23, 2021 at 7:24 AM tl455047 <tl445047925@gmail.com> wrote:
>
> Fixed a typo in comment.
>
> Signed-off-by: tl455047 <tl445047925@gmail.com>
Reviewed-by: Dmitry Vyukov <dvyukov@google.com>
+Andrew, linux-mm as KCOV patches are generally merged into mm.
Thanks for the fix
> ---
> kernel/kcov.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/kcov.c b/kernel/kcov.c
> index 80bfe71bbe13..6f59842f2caf 100644
> --- a/kernel/kcov.c
> +++ b/kernel/kcov.c
> @@ -527,7 +527,7 @@ static int kcov_get_mode(unsigned long arg)
>
> /*
> * Fault in a lazily-faulted vmalloc area before it can be used by
> - * __santizer_cov_trace_pc(), to avoid recursion issues if any code on the
> + * __sanitizer_cov_trace_pc(), to avoid recursion issues if any code on the
> * vmalloc fault handling path is instrumented.
> */
> static void kcov_fault_in_area(struct kcov *kcov)
> --
> 2.25.1
>
next prev parent reply other threads:[~2021-03-23 6:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 6:23 [PATCH] kernel: kcov: fix a typo in comment tl455047
2021-03-23 6:45 ` Dmitry Vyukov [this message]
2021-03-23 22:32 ` Marco Elver
2021-03-24 23:03 ` Andrew Morton
2021-03-24 23:11 ` Marco Elver
2021-03-24 7:10 Tim Yang
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=CACT4Y+atQZKKQqdUrk-JvQNXaZCBHz0S_tSkFuOA+nkTS4eoHg@mail.gmail.com \
--to=dvyukov@google.com \
--cc=akpm@linux-foundation.org \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tl445047925@gmail.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;
as well as URLs for NNTP newsgroup(s).