From: Borislav Petkov <bp@alien8.de>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: include/net/tcp_memcontrol.h:4:54: warning: ‘struct cgroup_subsys’ declared inside parameter list
Date: Sat, 16 Jan 2016 17:48:33 +0100 [thread overview]
Message-ID: <20160116164833.GD31869@pd.tnic> (raw)
Moin Johannes,
you're the last touching net/ipv4/tcp_memcontrol.c, so here you go :-P
In file included from net/ipv4/tcp_ipv4.c:76:0:
include/net/tcp_memcontrol.h:4:54: warning: ‘struct cgroup_subsys’ declared inside parameter list
int tcp_init_cgroup(struct mem_cgroup *memcg, struct cgroup_subsys *ss);
^
include/net/tcp_memcontrol.h:4:54: warning: its scope is only this definition or declaration, which is probably not what you want
In file included from net/ipv6/tcp_ipv6.c:64:0:
include/net/tcp_memcontrol.h:4:54: warning: ‘struct cgroup_subsys’ declared inside parameter list
int tcp_init_cgroup(struct mem_cgroup *memcg, struct cgroup_subsys *ss);
^
include/net/tcp_memcontrol.h:4:54: warning: its scope is only this definition or declaration, which is probably not what you want
In file included from net/ipv4/sysctl_net_ipv4.c:27:0:
include/net/tcp_memcontrol.h:4:54: warning: ‘struct cgroup_subsys’ declared inside parameter list
int tcp_init_cgroup(struct mem_cgroup *memcg, struct cgroup_subsys *ss);
^
include/net/tcp_memcontrol.h:4:54: warning: its scope is only this definition or declaration, which is probably not what you want
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next reply other threads:[~2016-01-16 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-16 16:48 Borislav Petkov [this message]
2016-01-18 0:05 ` include/net/tcp_memcontrol.h:4:54: warning: ‘struct cgroup_subsys’ declared inside parameter list Johannes Weiner
2016-01-18 0:10 ` Borislav Petkov
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=20160116164833.GD31869@pd.tnic \
--to=bp@alien8.de \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.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 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.