From mboxrd@z Thu Jan 1 00:00:00 1970 From: kbuild test robot Subject: Re: [PATCH bpf-next 1/2] bpf: enable stackmap with build_id in nmi context Date: Wed, 2 May 2018 11:34:25 +0800 Message-ID: <201805021107.ZO1QsYwr%fengguang.wu@intel.com> References: <20180502000220.2585320-1-songliubraving@fb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kbuild-all@01.org, netdev@vger.kernel.org, Song Liu , kernel-team@fb.com, Alexei Starovoitov , Daniel Borkmann , Peter Zijlstra To: Song Liu Return-path: Received: from mga11.intel.com ([192.55.52.93]:27540 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750823AbeEBDev (ORCPT ); Tue, 1 May 2018 23:34:51 -0400 Content-Disposition: inline In-Reply-To: <20180502000220.2585320-1-songliubraving@fb.com> Sender: netdev-owner@vger.kernel.org List-ID: Hi Song, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on bpf-next/master] url: https://github.com/0day-ci/linux/commits/Song-Liu/bpf-enable-stackmap-with-build_id-in-nmi-context/20180502-081727 base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master reproduce: # apt-get install sparse make ARCH=x86_64 allmodconfig make C=1 CF=-D__CHECK_ENDIAN__ sparse warnings: (new ones prefixed by >>) >> kernel/bpf/stackmap.c:51:1: sparse: symbol '__pcpu_scope_irq_work' was not declared. Should it be static? Please review and possibly fold the followup patch. --- 0-DAY kernel test infrastructure Open Source Technology Center https://lists.01.org/pipermail/kbuild-all Intel Corporation