From: kbuild test robot <lkp@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: Alexei Starovoitov <ast@fb.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
kbuild-all@01.org, Tejun Heo <tj@kernel.org>,
cgroups@vger.kernel.org, Roman Gushchin <guro@fb.com>
Subject: [RFC PATCH] cgroup: cgroup_idr_lock can be static
Date: Mon, 19 Mar 2018 13:41:27 +0800 [thread overview]
Message-ID: <20180319054127.GA6844@intel17> (raw)
In-Reply-To: <20180317000905.7091-2-matthew.d.roper@intel.com>
Fixes: d6de4e7e9e60 ("cgroup: Allow registration and lookup of cgroup private data (v2)")
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
cgroup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/cgroup/cgroup.c b/kernel/cgroup/cgroup.c
index c778830..9af6086 100644
--- a/kernel/cgroup/cgroup.c
+++ b/kernel/cgroup/cgroup.c
@@ -91,7 +91,7 @@ static DEFINE_IDR(cgroup_priv_idr);
* Protects cgroup_idr, css_idr, and cgroup_priv_idr so that IDs can be
* released without grabbing cgroup_mutex.
*/
-DEFINE_SPINLOCK(cgroup_idr_lock);
+static DEFINE_SPINLOCK(cgroup_idr_lock);
/*
* Protects cgroup_file->kn for !self csses. It synchronizes notifications
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-03-19 5:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-17 0:08 [PATCH v4 0/8] cgroup private data and DRM/i915 integration Matt Roper
2018-03-17 0:08 ` [PATCH v4 1/8] cgroup: Allow registration and lookup of cgroup private data (v2) Matt Roper
2018-03-19 5:41 ` kbuild test robot [this message]
2018-03-19 5:41 ` [Intel-gfx] " kbuild test robot
2018-03-17 0:08 ` [PATCH v4 2/8] cgroup: Introduce task_get_dfl_cgroup() (v2) Matt Roper
2018-03-17 0:09 ` [PATCH v4 3/8] cgroup: Introduce cgroup_priv_get_current Matt Roper
2018-03-17 0:09 ` [PATCH v4 4/8] drm/i915: Adjust internal priority definitions Matt Roper
2018-03-17 0:09 ` [PATCH v4 5/8] drm/i915: cgroup integration (v3) Matt Roper
2018-03-17 0:09 ` [PATCH v4 6/8] drm/i915: Introduce 'priority offset' for GPU contexts (v3) Matt Roper
2018-03-17 0:09 ` [PATCH v4 7/8] drm/i915: Introduce per-cgroup display boost setting Matt Roper
2018-03-17 0:09 ` [PATCH v4 8/8] drm/i915: Add context priority & priority offset to debugfs (v2) Matt Roper
2018-03-17 0:16 ` [PATCH i-g-t] tests: Introduce drv_cgroup (v2) Matt Roper
2018-03-17 0:28 ` ✗ Fi.CI.CHECKPATCH: warning for cgroup private data and DRM/i915 integration Patchwork
2018-03-19 7:43 ` Jani Nikula
2018-03-17 0:45 ` ✓ Fi.CI.BAT: success " Patchwork
2018-03-17 1:04 ` ✓ Fi.CI.BAT: success for tests: Introduce drv_cgroup (v2) Patchwork
2018-03-23 12:15 ` [PATCH v4 0/8] cgroup private data and DRM/i915 integration Joonas Lahtinen
2018-03-23 15:46 ` Matt Roper
2018-03-26 7:30 ` Joonas Lahtinen
2018-03-30 0:43 ` Matt Roper
2018-04-05 13:46 ` DRM cgroups integration (Was: Re: [PATCH v4 0/8] cgroup private data and DRM/i915 integration) Joonas Lahtinen
2018-04-05 14:15 ` Joonas Lahtinen
2018-04-05 14:49 ` Matt Roper
2018-04-05 15:06 ` Matt Roper
2018-04-05 15:48 ` Matt Roper
2018-04-05 17:32 ` Felix Kuehling
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=20180319054127.GA6844@intel17 \
--to=lkp@intel.com \
--cc=ast@fb.com \
--cc=cgroups@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=guro@fb.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kbuild-all@01.org \
--cc=matthew.d.roper@intel.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).