From: YueHaibing <yuehaibing@huawei.com>
To: <ast@kernel.org>, <daniel@iogearbox.net>
Cc: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>
Subject: Re: [PATCH bpf-next] bpfilter: Fix mismatch in function argument types
Date: Thu, 19 Jul 2018 15:55:55 +0800 [thread overview]
Message-ID: <66c14347-6006-08f8-1b32-b3ba6b9fa6bb@huawei.com> (raw)
In-Reply-To: <20180719072556.20076-1-yuehaibing@huawei.com>
send wrong patch ,pls ignore it.
On 2018/7/19 15:25, YueHaibing wrote:
> Fix following warning:
> net/ipv4/bpfilter/sockopt.c:28:5: error: symbol 'bpfilter_ip_set_sockopt' redeclared with different type
> net/ipv4/bpfilter/sockopt.c:34:5: error: symbol 'bpfilter_ip_get_sockopt' redeclared with different type
>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> ---
> include/linux/bpfilter.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/bpfilter.h b/include/linux/bpfilter.h
> index 687b176..43acfa8 100644
> --- a/include/linux/bpfilter.h
> +++ b/include/linux/bpfilter.h
> @@ -5,9 +5,9 @@
> #include <uapi/linux/bpfilter.h>
>
> struct sock;
> -int bpfilter_ip_set_sockopt(struct sock *sk, int optname, char *optval,
> +int bpfilter_ip_set_sockopt(struct sock *sk, int optname, char __user *optval,
> unsigned int optlen);
> -int bpfilter_ip_get_sockopt(struct sock *sk, int optname, char *optval,
> +int bpfilter_ip_get_sockopt(struct sock *sk, int optname, char __user *optval,
> int *optlen);
> extern int (*bpfilter_process_sockopt)(struct sock *sk, int optname,
> char __user *optval,
>
prev parent reply other threads:[~2018-07-19 7:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 7:25 [PATCH bpf-next] bpfilter: Fix mismatch in function argument types YueHaibing
2018-07-19 7:55 ` YueHaibing [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=66c14347-6006-08f8-1b32-b3ba6b9fa6bb@huawei.com \
--to=yuehaibing@huawei.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--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