From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: linux-kernel@lists.codethink.co.uk,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: diag: add missing declarations
Date: Thu, 9 Jun 2016 15:17:29 +0100 [thread overview]
Message-ID: <b53b6dec-944a-aea2-ad86-423846cdae0a@codethink.co.uk> (raw)
In-Reply-To: <1465481446.7945.40.camel@edumazet-glaptop3.roam.corp.google.com>
On 09/06/16 15:10, Eric Dumazet wrote:
> On Thu, 2016-06-09 at 12:17 +0100, Ben Dooks wrote:
>> The functions inet_diag_msg_common_fill and inet_diag_msg_attrs_fill
>> seem to have been missed from the include/linux/inet_diag.h header
>> file. Add them to fix the following warnings:
>>
>> net/ipv4/inet_diag.c:69:6: warning: symbol 'inet_diag_msg_common_fill' was not declared. Should it be static?
>> net/ipv4/inet_diag.c:108:5: warning: symbol 'inet_diag_msg_attrs_fill' was not declared. Should it be static?
>>
>> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
>> ---
>> Cc: "David S. Miller" <davem@davemloft.net>
>> Cc: netdev@vger.kernel.org
>> Cc: linux-kernel@vger.kernel.org
>> ---
>> include/linux/inet_diag.h | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/include/linux/inet_diag.h b/include/linux/inet_diag.h
>> index 7c27fa1..feb04ea 100644
>> --- a/include/linux/inet_diag.h
>> +++ b/include/linux/inet_diag.h
>> @@ -52,6 +52,12 @@ struct sock *inet_diag_find_one_icsk(struct net *net,
>>
>> int inet_diag_bc_sk(const struct nlattr *_bc, struct sock *sk);
>>
>> +void inet_diag_msg_common_fill(struct inet_diag_msg *r, struct sock *sk);
>> +
>> +int inet_diag_msg_attrs_fill(struct sock *sk, struct sk_buff *skb,
>> + struct inet_diag_msg *r, int ext,
>> + struct user_namespace *user_ns);
>> +
>> extern int inet_diag_register(const struct inet_diag_handler *handler);
>> extern void inet_diag_unregister(const struct inet_diag_handler *handler);
>> #endif /* _INET_DIAG_H_ */
>
> Please send a v2, deleting them from net/sctp/sctp_diag.c
Ah, didn't spot those. Will send a second version thanks.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
prev parent reply other threads:[~2016-06-09 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 11:17 Ben Dooks
2016-06-09 14:10 ` Eric Dumazet
2016-06-09 14:17 ` Ben Dooks [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=b53b6dec-944a-aea2-ad86-423846cdae0a@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@lists.codethink.co.uk \
--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
all inboxes | Powered by JetHome®