From: Marco Elver <elver@google.com>
To: elver@google.com, akpm@linux-foundation.org
Cc: glider@google.com, dvyukov@google.com, andreyknvl@google.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kasan-dev@googlegroups.com
Subject: [PATCH mm 3/4] kfence, arm64: add missing copyright and description header
Date: Mon, 18 Jan 2021 10:21:58 +0100 [thread overview]
Message-ID: <20210118092159.145934-3-elver@google.com> (raw)
In-Reply-To: <20210118092159.145934-1-elver@google.com>
Add missing copyright and description header to KFENCE source file.
Signed-off-by: Marco Elver <elver@google.com>
---
If appropriate, to be squashed into:
arm64, kfence: enable KFENCE for ARM64
---
arch/arm64/include/asm/kfence.h | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/include/asm/kfence.h b/arch/arm64/include/asm/kfence.h
index 6c0afeeab635..d061176d57ea 100644
--- a/arch/arm64/include/asm/kfence.h
+++ b/arch/arm64/include/asm/kfence.h
@@ -1,4 +1,9 @@
/* SPDX-License-Identifier: GPL-2.0 */
+/*
+ * arm64 KFENCE support.
+ *
+ * Copyright (C) 2020, Google LLC.
+ */
#ifndef __ASM_KFENCE_H
#define __ASM_KFENCE_H
--
2.30.0.284.gd98b1dd5eaa7-goog
next prev parent reply other threads:[~2021-01-18 9:39 UTC|newest]
Thread overview: 8+ 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 ` [PATCH mm 2/4] kfence, x86: add missing copyright and description header Marco Elver
2021-01-18 10:28 ` Alexander Potapenko
2021-01-18 9:21 ` Marco Elver [this message]
2021-01-18 10:28 ` [PATCH mm 3/4] kfence, arm64: " Alexander Potapenko
2021-01-18 9:21 ` [PATCH mm 4/4] kfence: add missing copyright header to documentation Marco Elver
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
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=20210118092159.145934-3-elver@google.com \
--to=elver@google.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=dvyukov@google.com \
--cc=glider@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 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).