From: patchwork-bot+netdevbpf@kernel•org
To: Hailong Liu <liuhailongg6@163•com>
Cc: ast@kernel•org, yhs@fb•com, daniel@iogearbox•net,
andrii@kernel•org, kafai@fb•com, songliubraving@fb•com,
john.fastabend@gmail•com, kpsingh@kernel•org,
netdev@vger•kernel.org, bpf@vger•kernel.org,
linux-kernel@vger•kernel.org, liu.hailong6@zte•com.cn
Subject: Re: [PATCH] samples, bpf: suppress compiler warning
Date: Wed, 12 May 2021 19:40:10 +0000 [thread overview]
Message-ID: <162084841010.1089.2404998969995736892.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210511140429.89426-1-liuhailongg6@163.com>
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Tue, 11 May 2021 22:04:29 +0800 you wrote:
> From: Hailong Liu <liu.hailong6@zte•com.cn>
>
> While cross compiling on ARM32 , the casting from pointer to __u64 will
> cause warnings:
>
> samples/bpf/task_fd_query_user.c: In function 'main':
> samples/bpf/task_fd_query_user.c:399:23: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
> 399 | uprobe_file_offset = (__u64)main - (__u64)&__executable_start;
> | ^
> samples/bpf/task_fd_query_user.c:399:37: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
> 399 | uprobe_file_offset = (__u64)main - (__u64)&__executable_start;
>
> [...]
Here is the summary with links:
- samples, bpf: suppress compiler warning
https://git.kernel.org/bpf/bpf-next/c/0303ce17347a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-05-12 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 14:04 [PATCH] samples, bpf: suppress compiler warning Hailong Liu
2021-05-12 19:40 ` patchwork-bot+netdevbpf [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=162084841010.1089.2404998969995736892.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=andrii@kernel$(echo .)org \
--cc=ast@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=daniel@iogearbox$(echo .)net \
--cc=john.fastabend@gmail$(echo .)com \
--cc=kafai@fb$(echo .)com \
--cc=kpsingh@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=liu.hailong6@zte$(echo .)com.cn \
--cc=liuhailongg6@163$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=songliubraving@fb$(echo .)com \
--cc=yhs@fb$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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