From: David Miller <davem@davemloft.net>
To: geert@linux-m68k.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tcp_memcontrol: Forward declare cgroup_subsys and mem_cgroup stucts
Date: Sun, 17 Jan 2016 12:02:48 -0500 (EST) [thread overview]
Message-ID: <20160117.120248.1797719628794320481.davem@davemloft.net> (raw)
In-Reply-To: <1453026637-9942-1-git-send-email-geert@linux-m68k.org>
From: Geert Uytterhoeven <geert@linux-m68k.org>
Date: Sun, 17 Jan 2016 11:30:37 +0100
> In file included from net/ipv4/tcp_ipv4.c:77 (and many more):
> include/net/tcp_memcontrol.h:5: warning: ‘struct cgroup_subsys’ declared inside parameter list
> include/net/tcp_memcontrol.h:5: warning: its scope is only this definition or declaration, which is probably not what you want
>
> Add forward declarations for all used structures to fix this.
>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Applied, thanks Geert.
prev parent reply other threads:[~2016-01-17 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 10:30 [PATCH] tcp_memcontrol: Forward declare cgroup_subsys and mem_cgroup stucts Geert Uytterhoeven
2016-01-17 17:02 ` David Miller [this message]
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=20160117.120248.1797719628794320481.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox