From: Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: Greg KH <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
Cc: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] cgroup.h: remove some functions that are now gone
Date: Mon, 6 May 2013 08:50:19 +0800 [thread overview]
Message-ID: <5186FE4B.1050501@huawei.com> (raw)
In-Reply-To: <20130503232659.GA12008-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
On 2013/5/4 7:26, Greg KH wrote:
> From: Greg KH <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
>
> cgroup_lock() and cgroup_unlock() are now no longer exported, so fix
> cgroup.h to not declare them if CONFIG_CGROUPS is not enabled.
>
> Signed-off-by: Greg Kroah-Hartman <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
Acked-by: Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
>
> diff --git a/include/linux/cgroup.h b/include/linux/cgroup.h
> index 3bff9ce..e2ab34d 100644
> --- a/include/linux/cgroup.h
> +++ b/include/linux/cgroup.h
> @@ -837,8 +837,6 @@ static inline void cgroup_fork(struct task_struct *p) {}
> static inline void cgroup_post_fork(struct task_struct *p) {}
> static inline void cgroup_exit(struct task_struct *p, int callbacks) {}
>
> -static inline void cgroup_lock(void) {}
> -static inline void cgroup_unlock(void) {}
> static inline int cgroupstats_build(struct cgroupstats *stats,
> struct dentry *dentry)
> {
>
next prev parent reply other threads:[~2013-05-06 0:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 23:26 [PATCH] cgroup.h: remove some functions that are now gone Greg KH
[not found] ` <20130503232659.GA12008-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2013-05-06 0:50 ` Li Zefan
2013-05-06 0:50 ` Li Zefan [this message]
2013-05-06 19:08 ` Tejun Heo
2013-05-06 19:08 ` Tejun Heo
2013-05-14 18:51 ` Tejun Heo
2013-05-14 18:51 ` 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=5186FE4B.1050501@huawei.com \
--to=lizefan-hv44wf8li93qt0dzr+alfa@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.