From: Daniel Borkmann <daniel@iogearbox.net>
To: Andrii Nakryiko <andriin@fb.com>,
bpf@vger.kernel.org, netdev@vger.kernel.org, ast@fb.com
Cc: andrii.nakryiko@gmail.com, kernel-team@fb.com
Subject: Re: [PATCH bpf-next 1/2] libbpf: fix another __u64 cast in printf
Date: Fri, 4 Sep 2020 15:09:14 +0200 [thread overview]
Message-ID: <8efdf19f-9353-b38f-e5c6-c4f3074ff591@iogearbox.net> (raw)
In-Reply-To: <20200904041611.1695163-1-andriin@fb.com>
On 9/4/20 6:16 AM, Andrii Nakryiko wrote:
> Another issue of __u64 needing either %lu or %llu, depending on the
> architecture. Fix with cast to `unsigned long long`.
>
> Fixes: 7e06aad52929 ("libbpf: Add multi-prog section support for struct_ops")
> Signed-off-by: Andrii Nakryiko <andriin@fb.com>
Applied, thanks!
prev parent reply other threads:[~2020-09-04 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 4:16 [PATCH bpf-next 1/2] libbpf: fix another __u64 cast in printf Andrii Nakryiko
2020-09-04 4:16 ` [PATCH bpf-next 2/2] libbpf: fix potential multiplication overflow Andrii Nakryiko
2020-09-04 13:09 ` Daniel Borkmann [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=8efdf19f-9353-b38f-e5c6-c4f3074ff591@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=andrii.nakryiko@gmail.com \
--cc=andriin@fb.com \
--cc=ast@fb.com \
--cc=bpf@vger.kernel.org \
--cc=kernel-team@fb.com \
--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;
as well as URLs for NNTP newsgroup(s).