From: Alexander Potapenko <glider@google.com>
To: Marco Elver <elver@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Dmitriy Vyukov <dvyukov@google.com>,
Andrey Konovalov <andreyknvl@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
kasan-dev <kasan-dev@googlegroups.com>
Subject: Re: [PATCH mm 4/4] kfence: add missing copyright header to documentation
Date: Mon, 18 Jan 2021 11:29:59 +0100 [thread overview]
Message-ID: <CAG_fn=W6vHmFs+FhCja_4XkSOUqkWTGOrw73=YY5Rz-O=SpU9g@mail.gmail.com> (raw)
In-Reply-To: <20210118092159.145934-4-elver@google.com>
On Mon, Jan 18, 2021 at 10:22 AM Marco Elver <elver@google.com> wrote:
>
> Add missing copyright header to KFENCE documentation.
>
> Signed-off-by: Marco Elver <elver@google.com>
Reviewed-by: Alexander Potapenko <glider@google.com>
next prev parent reply other threads:[~2021-01-18 10:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 9:21 [PATCH mm 1/4] kfence: add missing copyright and description headers Marco Elver
2021-01-18 9:21 ` Marco Elver
2021-01-18 9:21 ` [PATCH mm 2/4] kfence, x86: add missing copyright and description header Marco Elver
2021-01-18 9:21 ` Marco Elver
2021-01-18 10:28 ` Alexander Potapenko
2021-01-18 10:28 ` Alexander Potapenko
2021-01-18 9:21 ` [PATCH mm 3/4] kfence, arm64: " Marco Elver
2021-01-18 9:21 ` Marco Elver
2021-01-18 10:28 ` Alexander Potapenko
2021-01-18 10:28 ` Alexander Potapenko
2021-01-18 9:21 ` [PATCH mm 4/4] kfence: add missing copyright header to documentation Marco Elver
2021-01-18 9:21 ` Marco Elver
2021-01-18 10:29 ` Alexander Potapenko [this message]
2021-01-18 10:29 ` Alexander Potapenko
2021-01-18 10:28 ` [PATCH mm 1/4] kfence: add missing copyright and description headers Alexander Potapenko
2021-01-18 10:28 ` Alexander Potapenko
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='CAG_fn=W6vHmFs+FhCja_4XkSOUqkWTGOrw73=YY5Rz-O=SpU9g@mail.gmail.com' \
--to=glider@google.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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.