From: "Björn Töpel" <bjorn.topel@intel.com>
To: "kbuild test robot" <lkp@intel.com>,
"Björn Töpel" <bjorn.topel@gmail.com>,
ast@kernel.org, daniel@iogearbox.net, davem@davemloft.net,
kuba@kernel.org, hawk@kernel.org, john.fastabend@gmail.com,
netdev@vger.kernel.org, bpf@vger.kernel.org,
magnus.karlsson@intel.com, jonathan.lemon@gmail.com,
jeffrey.t.kirsher@intel.com
Cc: kbuild-all@lists.01.org, maximmi@mellanox.com,
maciej.fijalkowski@intel.com, intel-wired-lan@lists.osuosl.org
Subject: Re: [PATCH bpf-next v3 07/15] i40e: separate kernel allocated rx_bi rings from AF_XDP rings
Date: Tue, 19 May 2020 18:20:09 +0200 [thread overview]
Message-ID: <c81b36a0-11dd-4b7f-fad8-85f31dced58c@intel.com> (raw)
In-Reply-To: <202005192351.j1H08VpV%lkp@intel.com>
On 2020-05-19 17:18, kbuild test robot wrote:
> Hi "Björn,
>
> I love your patch! Perhaps something to improve:
>
> [auto build test WARNING on bpf-next/master]
> [also build test WARNING on jkirsher-next-queue/dev-queue next-20200518]
> [cannot apply to bpf/master linus/master v5.7-rc6]
> [if your patch is applied to the wrong git tree, please drop us a note to help
> improve the system. BTW, we also suggest to use '--base' option to specify the
> base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
>
> url: https://github.com/0day-ci/linux/commits/Bj-rn-T-pel/Introduce-AF_XDP-buffer-allocation-API/20200519-203122
> base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
> config: riscv-allyesconfig (attached as .config)
> compiler: riscv64-linux-gcc (GCC) 9.3.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=riscv
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>, old ones prefixed by <<):
>
>>> drivers/net/ethernet/intel/i40e/i40e_txrx.c:531:6: warning: no previous prototype for 'i40e_fd_handle_status' [-Wmissing-prototypes]
> 531 | void i40e_fd_handle_status(struct i40e_ring *rx_ring, u64 qword0_raw,
> | ^~~~~~~~~~~~~~~~~~~~~
>
Yes, this could indeed be made static. Hmm, I wonder why I didn't get
that warning on my x86-64 build!? I'll spin a v4 (or do a follow-up?).
Björn
next prev parent reply other threads:[~2020-05-19 16:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 8:57 [PATCH bpf-next v3 00/15] Introduce AF_XDP buffer allocation API Björn Töpel
2020-05-19 8:57 ` [PATCH bpf-next v3 01/15] xsk: fix xsk_umem_xdp_frame_sz() Björn Töpel
2020-05-19 8:57 ` [PATCH bpf-next v3 02/15] xsk: move xskmap.c to net/xdp/ Björn Töpel
2020-05-19 8:57 ` [PATCH bpf-next v3 03/15] xsk: move driver interface to xdp_sock_drv.h Björn Töpel
2020-05-19 8:57 ` [PATCH bpf-next v3 04/15] xsk: move defines only used by AF_XDP internals to xsk.h Björn Töpel
2020-05-19 8:57 ` [PATCH bpf-next v3 05/15] xsk: introduce AF_XDP buffer allocation API Björn Töpel
2020-05-19 8:57 ` [PATCH bpf-next v3 06/15] i40e: refactor rx_bi accesses Björn Töpel
2020-05-19 8:57 ` [PATCH bpf-next v3 07/15] i40e: separate kernel allocated rx_bi rings from AF_XDP rings Björn Töpel
2020-05-19 15:18 ` kbuild test robot
2020-05-19 16:20 ` Björn Töpel [this message]
2020-05-19 16:55 ` Jakub Kicinski
2020-05-19 17:06 ` Björn Töpel
2020-05-19 8:57 ` [PATCH bpf-next v3 08/15] i40e, xsk: migrate to new MEM_TYPE_XSK_BUFF_POOL Björn Töpel
2020-05-19 8:57 ` [PATCH bpf-next v3 09/15] ice, " Björn Töpel
2020-05-19 8:57 ` [PATCH bpf-next v3 10/15] ixgbe, " Björn Töpel
2020-05-19 8:57 ` [PATCH bpf-next v3 11/15] mlx5, " Björn Töpel
2020-05-19 8:57 ` [PATCH bpf-next v3 12/15] xsk: remove MEM_TYPE_ZERO_COPY and corresponding code Björn Töpel
2020-05-19 8:57 ` [PATCH bpf-next v3 13/15] xdp: simplify xdp_return_{frame,frame_rx_napi,buff} Björn Töpel
2020-05-19 8:57 ` [PATCH bpf-next v3 14/15] xsk: explicitly inline functions and move definitions Björn Töpel
2020-05-19 8:57 ` [PATCH bpf-next v3 15/15] MAINTAINERS, xsk: update AF_XDP section after moves/adds Björn Töpel
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=c81b36a0-11dd-4b7f-fad8-85f31dced58c@intel.com \
--to=bjorn.topel@intel.com \
--cc=ast@kernel.org \
--cc=bjorn.topel@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=john.fastabend@gmail.com \
--cc=jonathan.lemon@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=kuba@kernel.org \
--cc=lkp@intel.com \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=maximmi@mellanox.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).