From: Vivek Goyal <vgoyal@redhat.com>
To: linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
netdev@vger.kernel.org, davem@davemloft.net, tj@kernel.org
Cc: ssorce@redhat.com, jkaluza@redhat.com, lpoetter@redhat.com,
kay@redhat.com, Vivek Goyal <vgoyal@redhat.com>
Subject: [PATCH 1/2] cgroup: Provide empty definition of task_cgroup_path()
Date: Wed, 12 Mar 2014 14:45:41 -0400 [thread overview]
Message-ID: <1394649942-5854-2-git-send-email-vgoyal@redhat.com> (raw)
In-Reply-To: <1394649942-5854-1-git-send-email-vgoyal@redhat.com>
Compilation with !CONFIG_CGROUP fails for task_cgroup_path() user. So
provide an emtpy definition.
Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
---
include/linux/cgroup.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/cgroup.h b/include/linux/cgroup.h
index 9450f02..bf40adb 100644
--- a/include/linux/cgroup.h
+++ b/include/linux/cgroup.h
@@ -869,6 +869,8 @@ static inline int cgroup_attach_task_all(struct task_struct *from,
return 0;
}
+static inline int task_cgroup_path(struct task_struct *task, char *buf, size_t buflen) {return 0;}
+
#endif /* !CONFIG_CGROUPS */
#endif /* _LINUX_CGROUP_H */
--
1.8.5.3
next prev parent reply other threads:[~2014-03-12 18:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 18:45 [PATCH 0/2] net: Implement SO_PEERCGROUP to get cgroup of peer Vivek Goyal
2014-03-12 18:45 ` Vivek Goyal [this message]
2014-03-12 19:00 ` [PATCH 1/2] cgroup: Provide empty definition of task_cgroup_path() David Miller
2014-03-12 20:13 ` Vivek Goyal
2014-03-12 18:45 ` [PATCH 2/2] net: Implement SO_PEERCGROUP Vivek Goyal
2014-03-12 20:46 [PATCH 0/2][V2] net: Implement SO_PEERCGROUP to get cgroup of peer Vivek Goyal
2014-03-12 20:46 ` [PATCH 1/2] cgroup: Provide empty definition of task_cgroup_path() Vivek Goyal
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=1394649942-5854-2-git-send-email-vgoyal@redhat.com \
--to=vgoyal@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=jkaluza@redhat.com \
--cc=kay@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lpoetter@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=ssorce@redhat.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
Powered by JetHome