From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Li Zefan <lizefan@huawei.com>,
Johannes Weiner <hannes@cmpxchg.org>,
cgroups@vger.kernel.org
Subject: [GIT PULL] cgroup changes for v4.16-rc1
Date: Tue, 30 Jan 2018 10:35:52 -0800 [thread overview]
Message-ID: <20180130183552.GJ1121507@devbig577.frc2.facebook.com> (raw)
Hello, Linus.
Nothing too interesting. Documentation updates and trivial changes;
however, this pull request does containt he previusly discussed
dropping of __must_check from strscpy().
Thanks.
The following changes since commit 4f58424da3deead2605e39a9df65f5f06107a3cb:
cgroup: make cgroup.threads delegatable (2018-01-10 09:42:32 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-4.16
for you to fetch changes up to 03eac8b22194becd77d253fc546429ebb544aebf:
Documentation: Fix 'file_mapped' -> 'mapped_file' (2018-01-30 09:52:11 -0800)
----------------------------------------------------------------
Florian Schmidt (1):
Documentation: Fix 'file_mapped' -> 'mapped_file'
Maciej S. Szmigiero (1):
cgroup, docs: document the root cgroup behavior of cpu and io controllers
Matt Roper (2):
Documentation/cgroup-v1: fix outdated programming details
cgroup: Update documentation reference
Roman Gushchin (1):
cgroup, docs: document cgroup v2 device controller
Tejun Heo (2):
Merge branch 'for-4.15-fixes' into for-4.16
string: drop __must_check from strscpy() and restore strscpy() usages in cgroup
Vladimir Rutsky (1):
cgroup-v2.txt: fix typos
Documentation/cgroup-v1/cgroups.txt | 7 +---
Documentation/cgroup-v1/memory.txt | 4 +-
Documentation/cgroup-v2.txt | 77 ++++++++++++++++++++++++++++++++-----
include/linux/cgroup-defs.h | 2 +-
include/linux/string.h | 2 +-
kernel/cgroup/cgroup.c | 6 +--
6 files changed, 76 insertions(+), 22 deletions(-)
--
tejun
reply other threads:[~2018-01-30 18:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180130183552.GJ1121507@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=torvalds@linux-foundation.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
Powered by JetHome