[PATCH] net: ipconfgi: add declaration for ic_addrservaddr

The symbol ic_addrservaddr is not static, but has no declaration
to match. Since the similar variables are all exported, add this
one to the header file as well.

This fixes the following warning:

net/ipv4/ipconfig.c:130:8: warning: symbol 'ic_addrservaddr' was not declared. Should it be static?

Signed-off-by: Ben Dooks <redacted>
---
Cc: "David S. Miller" <davem@davemloft.net>
Cc: Alexey Kuznetsov <redacted>
Cc: James Morris <jmorris@namei.org>
Cc: Hideaki YOSHIFUJI <redacted>
Cc: Patrick McHardy <redacted>
Cc: netdev@vger.kernel.org
---
 include/net/ipconfig.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/include/net/ipconfig.h b/include/net/ipconfig.h
index c74cc1b..e5f4d6e 100644
--- a/include/net/ipconfig.h
+++ b/include/net/ipconfig.h

@@ -13,6 +13,7 @@ extern __be32 ic_myaddr;		/* My IP address */
 extern __be32 ic_gateway;		/* Gateway IP address */
 
 extern __be32 ic_servaddr;		/* Boot server IP address */
+extern __be32 ic_addrservaddr;		/* IP Address of the IP addresses'server */
 
 extern __be32 root_server_addr;	/* Address of NFS server */
 extern u8 root_server_path[];	/* Path to mount as root */

-- 
2.8.1

On 06/09/2016 01:07 PM, Ben Dooks wrote:

The symbol ic_addrservaddr is not static, but has no declaration
to match. Since the similar variables are all exported, add this
one to the header file as well.

This fixes the following warning:

net/ipv4/ipconfig.c:130:8: warning: symbol 'ic_addrservaddr' was not declared. Should it be static?

Signed-off-by: Ben Dooks <redacted>

Well, how about making it actually static if it's only used
from ipconfig.c ?

On 09/06/16 12:35, Daniel Borkmann wrote:

On 06/09/2016 01:07 PM, Ben Dooks wrote:

quoted

The symbol ic_addrservaddr is not static, but has no declaration
to match. Since the similar variables are all exported, add this
one to the header file as well.

This fixes the following warning:

net/ipv4/ipconfig.c:130:8: warning: symbol 'ic_addrservaddr' was not
declared. Should it be static?

Signed-off-by: Ben Dooks <redacted>

Well, how about making it actually static if it's only used
from ipconfig.c ?

The only reason is that I thought someone might want to
use it in the future. I have no particular insight though.

-- 
Ben Dooks				http://www.codethink.co.uk/
Senior Engineer				Codethink - Providing Genius

On 06/09/2016 02:11 PM, Ben Dooks wrote:

On 09/06/16 12:35, Daniel Borkmann wrote:

quoted

On 06/09/2016 01:07 PM, Ben Dooks wrote:

quoted

The symbol ic_addrservaddr is not static, but has no declaration
to match. Since the similar variables are all exported, add this
one to the header file as well.

This fixes the following warning:

net/ipv4/ipconfig.c:130:8: warning: symbol 'ic_addrservaddr' was not
declared. Should it be static?

Signed-off-by: Ben Dooks <redacted>

Well, how about making it actually static if it's only used
from ipconfig.c ?

The only reason is that I thought someone might want to
use it in the future. I have no particular insight though.

Usual policy is that if such thing is required, then it can be
exported along with the code that is making use of it from elsewhere.

Thanks,
Daniel

From: Daniel Borkmann <daniel@iogearbox.net>
Date: Thu, 09 Jun 2016 14:15:43 +0200

On 06/09/2016 02:11 PM, Ben Dooks wrote:

quoted

On 09/06/16 12:35, Daniel Borkmann wrote:

quoted

On 06/09/2016 01:07 PM, Ben Dooks wrote:

quoted

The symbol ic_addrservaddr is not static, but has no declaration
to match. Since the similar variables are all exported, add this
one to the header file as well.

This fixes the following warning:

net/ipv4/ipconfig.c:130:8: warning: symbol 'ic_addrservaddr' was not
declared. Should it be static?

Signed-off-by: Ben Dooks <redacted>

Well, how about making it actually static if it's only used
from ipconfig.c ?

The only reason is that I thought someone might want to
use it in the future. I have no particular insight though.

Usual policy is that if such thing is required, then it can be
exported along with the code that is making use of it from elsewhere.

Right.