From: "Björn Töpel" <bjorn.topel@gmail.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, Netdev <netdev@vger.kernel.org>,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Björn Töpel" <bjorn.topel@intel.com>, bpf <bpf@vger.kernel.org>,
"Magnus Karlsson" <magnus.karlsson@gmail.com>,
"Karlsson, Magnus" <magnus.karlsson@intel.com>,
"Jonathan Lemon" <jonathan.lemon@gmail.com>,
"Edward Cree" <ecree@solarflare.com>,
"Toke Høiland-Jørgensen" <thoiland@redhat.com>,
"Andrii Nakryiko" <andrii.nakryiko@gmail.com>
Subject: Re: [PATCH bpf-next 1/3] bpf: introduce BPF dispatcher
Date: Thu, 21 Nov 2019 10:23:31 +0100 [thread overview]
Message-ID: <CAJ+HfNiq4QhHbO5reVKC7n95unqVWHSRnX0-+HoqdHb3iXoUbQ@mail.gmail.com> (raw)
In-Reply-To: <201911211536.JzaBr1Ub%lkp@intel.com>
On Thu, 21 Nov 2019 at 08:27, kbuild test robot <lkp@intel.com> wrote:
>
[...]
> >> kernel/bpf/dispatcher.c:151:14: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
> *ipsp++ = (s64)d->progs[i]->bpf_func;
> ^
I'll fix the cast warning on i386 in the v2.
next prev parent reply other threads:[~2019-11-21 9:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 16:07 [PATCH bpf-next 0/3] Introduce xdp_call.h and the BPF dispatcher Björn Töpel
2019-11-19 16:07 ` [PATCH bpf-next 1/3] bpf: introduce " Björn Töpel
2019-11-21 7:27 ` kbuild test robot
2019-11-21 9:23 ` Björn Töpel [this message]
2019-11-23 0:25 ` [RFC PATCH] bpf: bpf_dispatcher_lookup() can be static kbuild test robot
2019-11-23 14:03 ` kbuild test robot
2019-11-19 16:07 ` [PATCH bpf-next 2/3] xdp: introduce xdp_call Björn Töpel
2019-11-19 16:07 ` [PATCH bpf-next 3/3] i40e: start using xdp_call.h Björn Töpel
2019-11-23 15:52 ` kbuild test robot
2019-11-23 15:52 ` [RFC PATCH] i40e: ____xdp_call_i40e_xdp_call_tramp can be static kbuild test robot
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=CAJ+HfNiq4QhHbO5reVKC7n95unqVWHSRnX0-+HoqdHb3iXoUbQ@mail.gmail.com \
--to=bjorn.topel@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bjorn.topel@intel.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=ecree@solarflare.com \
--cc=jonathan.lemon@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=lkp@intel.com \
--cc=magnus.karlsson@gmail.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=thoiland@redhat.com \
/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).