From: Igor Stoppa <igor.stoppa@gmail.com>
To: mhocko@kernel.org, akpm@linux-foundation.org,
keescook@chromium.org, linux-mm@kvack.org,
kernel-hardening@lists.openwall.com,
linux-security-module@vger.kernel.org
Cc: willy@infradead.org, labbott@redhat.com,
linux-kernel@vger.kernel.org, igor.stoppa@huawei.com
Subject: [PATCH 2/3] Add label and license to genalloc.rst
Date: Wed, 2 May 2018 05:05:21 +0400 [thread overview]
Message-ID: <20180502010522.28767-3-igor.stoppa@huawei.com> (raw)
In-Reply-To: <20180502010522.28767-1-igor.stoppa@huawei.com>
Add SPDX license to genalloc.rst, then a label, to allow cross-referencing.
Signed-off-by: Igor Stoppa <igor.stoppa@huawei.com>
---
Documentation/core-api/genalloc.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/core-api/genalloc.rst b/Documentation/core-api/genalloc.rst
index 6b38a39fab24..0b5ade832ee8 100644
--- a/Documentation/core-api/genalloc.rst
+++ b/Documentation/core-api/genalloc.rst
@@ -1,3 +1,7 @@
+.. SPDX-License-Identifier: GPL-2.0
+
+.. _genalloc:
+
The genalloc/genpool subsystem
==============================
--
2.14.1
next prev parent reply other threads:[~2018-05-02 1:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 1:05 [PATCH 0/3 v2] linux-next: mm: Track genalloc allocations Igor Stoppa
2018-05-02 1:05 ` [PATCH 1/3] genalloc: track beginning of allocations Igor Stoppa
2018-05-02 1:05 ` Igor Stoppa [this message]
2018-05-02 1:05 ` [PATCH 3/3] genalloc: selftest Igor Stoppa
2018-05-02 21:50 ` [PATCH 0/3 v2] linux-next: mm: Track genalloc allocations Andrew Morton
2018-05-02 23:02 ` Igor Stoppa
-- strict thread matches above, loose matches on Subject: below --
2018-04-29 2:45 [PATCH 0/3] linux-next: mm: hardening: " Igor Stoppa
2018-04-29 2:45 ` [PATCH 2/3] Add label and license to genalloc.rst Igor Stoppa
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=20180502010522.28767-3-igor.stoppa@huawei.com \
--to=igor.stoppa@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=igor.stoppa@huawei.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=willy@infradead.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).