From: Andrew Morton <akpm@linux-foundation.org>
To: Marco Elver <elver@google.com>
Cc: tl455047 <tl445047925@gmail.com>,
kasan-dev <kasan-dev@googlegroups.com>,
Dmitry Vyukov <dvyukov@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>
Subject: Re: [PATCH] kernel: kcov: fix a typo in comment
Date: Wed, 24 Mar 2021 16:03:58 -0700 [thread overview]
Message-ID: <20210324160358.0f36aa1f8ea7098f66fe64bd@linux-foundation.org> (raw)
In-Reply-To: <CANpmjNMFfQs6bV4wrigfcWMwCvA_oMwBxy9gkaD4g+A1sZJ6-Q@mail.gmail.com>
On Tue, 23 Mar 2021 23:32:57 +0100 Marco Elver <elver@google.com> wrote:
> On Tue, 23 Mar 2021 at 07:45, 'Dmitry Vyukov' via kasan-dev
> <kasan-dev@googlegroups.com> wrote:
> > 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
>
> FYI, I believe this code may not be accepted due to this:
>
> "[...] It is imperative that all code contributed to the kernel be legitimately
> free software. For that reason, code from anonymous (or pseudonymous)
> contributors will not be accepted."
>
> See Documentation/process/1.Intro.rst
Correct. I let this one pass because the patch is so minor. But yes,
a real name would be preferred, please.
next prev parent reply other threads:[~2021-03-24 23:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210323062303.19541-1-tl445047925@gmail.com>
2021-03-23 6:45 ` Dmitry Vyukov
2021-03-23 22:32 ` Marco Elver
2021-03-24 23:03 ` Andrew Morton [this message]
2021-03-24 23:11 ` Marco Elver
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=20210324160358.0f36aa1f8ea7098f66fe64bd@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--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