From: Rami Rosen <rami.rosen@intel.com>
To: cgroups@vger.kernel.org
Cc: tj@kernel.org, lizefan@huawei.com, hannes@cmpxchg.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
corbet@lwn.net, Rami Rosen <rami.rosen@intel.com>
Subject: [PATCH] Documentation: cgroup v1: remove section about subsystem as a module.
Date: Thu, 14 Jan 2016 15:46:05 +0200 [thread overview]
Message-ID: <1452779165-15567-1-git-send-email-rami.rosen@intel.com> (raw)
This patch removes the text relating to compiling cgroup as a module,
since commit 3ed80a62bf95 ("cgroup: drop module support") makes this text not
relevant anymore.
Signed-off-by: Rami Rosen <rami.rosen@intel.com>
---
Documentation/cgroup-v1/cgroups.txt | 5 -----
1 file changed, 5 deletions(-)
diff --git a/Documentation/cgroup-v1/cgroups.txt b/Documentation/cgroup-v1/cgroups.txt
index c6256ae..176f95e 100644
--- a/Documentation/cgroup-v1/cgroups.txt
+++ b/Documentation/cgroup-v1/cgroups.txt
@@ -525,11 +525,6 @@ Each subsystem should:
- add an entry in linux/cgroup_subsys.h
- define a cgroup_subsys object called <name>_subsys
-If a subsystem can be compiled as a module, it should also have in its
-module initcall a call to cgroup_load_subsys(), and in its exitcall a
-call to cgroup_unload_subsys(). It should also set its_subsys.module =
-THIS_MODULE in its .c file.
-
Each subsystem may export the following methods. The only mandatory
methods are css_alloc/free. Any others that are null are presumed to
be successful no-ops.
--
2.4.3
next reply other threads:[~2016-01-14 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 13:46 Rami Rosen [this message]
[not found] ` <1452779165-15567-1-git-send-email-rami.rosen-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-01-21 3:25 ` [PATCH] Documentation: cgroup v1: remove section about subsystem as a module Zefan Li
2016-01-22 16:11 ` Tejun Heo
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=1452779165-15567-1-git-send-email-rami.rosen@intel.com \
--to=rami.rosen@intel.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=hannes@cmpxchg.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=tj@kernel.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).