MPTCP Linux Development
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Geliang Tang <geliang.tang@suse.com>, mptcp@lists.linux.dev
Cc: kbuild-all@lists.01.org, Geliang Tang <geliang.tang@suse.com>
Subject: Re: [PATCH mptcp-next v5 05/11] mptcp: add bpf set scheduled helper
Date: Wed, 1 Jun 2022 17:25:04 +0800	[thread overview]
Message-ID: <202206011710.y7OIrPON-lkp@intel.com> (raw)
In-Reply-To: <af10cde0bfec857862b84ac9e2624a544ccd4795.1654065674.git.geliang.tang@suse.com>

Hi Geliang,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on mptcp/export]
[cannot apply to bpf-next/master bpf/master linus/master v5.18 next-20220601]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/intel-lab-lkp/linux/commits/Geliang-Tang/BPF-packet-scheduler/20220601-144812
base:   https://github.com/multipath-tcp/mptcp_net-next.git export
config: x86_64-randconfig-a006 (https://download.01.org/0day-ci/archive/20220601/202206011710.y7OIrPON-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-1) 11.3.0
reproduce (this is a W=1 build):
        # https://github.com/intel-lab-lkp/linux/commit/4bfb6a3d6d5ea1744a301d97642ff0077eb280f6
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review Geliang-Tang/BPF-packet-scheduler/20220601-144812
        git checkout 4bfb6a3d6d5ea1744a301d97642ff0077eb280f6
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash net/mptcp/

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

>> net/mptcp/bpf.c:165:6: warning: no previous prototype for 'bpf_mptcp_subflow_set_scheduled' [-Wmissing-prototypes]
     165 | void bpf_mptcp_subflow_set_scheduled(struct mptcp_subflow_context *subflow)
         |      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


vim +/bpf_mptcp_subflow_set_scheduled +165 net/mptcp/bpf.c

   164	
 > 165	void bpf_mptcp_subflow_set_scheduled(struct mptcp_subflow_context *subflow)
   166	{
   167		WRITE_ONCE(subflow->scheduled, true);
   168	}
   169	EXPORT_SYMBOL(bpf_mptcp_subflow_set_scheduled);
   170	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

  reply	other threads:[~2022-06-01  9:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-01  6:45 [PATCH mptcp-next v5 00/11] BPF packet scheduler Geliang Tang
2022-06-01  6:45 ` [PATCH mptcp-next v5 01/11] Squash to "mptcp: add struct mptcp_sched_ops" Geliang Tang
2022-06-01  6:45 ` [PATCH mptcp-next v5 02/11] Squash to "mptcp: add sched in mptcp_sock" Geliang Tang
2022-06-01  6:45 ` [PATCH mptcp-next v5 03/11] Squash to "mptcp: add get_subflow wrappers" Geliang Tang
2022-06-01  6:45 ` [PATCH mptcp-next v5 04/11] Squash to "mptcp: add bpf_mptcp_sched_ops" Geliang Tang
2022-06-01  6:45 ` [PATCH mptcp-next v5 05/11] mptcp: add bpf set scheduled helper Geliang Tang
2022-06-01  9:25   ` kernel test robot [this message]
2022-06-01  6:45 ` [PATCH mptcp-next v5 06/11] Squash to "selftests/bpf: add bpf_first scheduler" Geliang Tang
2022-06-01  6:45 ` [PATCH mptcp-next v5 07/11] Squash to "selftests/bpf: add bpf_first test" Geliang Tang
2022-06-01  6:45 ` [PATCH mptcp-next v5 08/11] selftests/bpf: add bpf_bkup scheduler Geliang Tang
2022-06-01  6:45 ` [PATCH mptcp-next v5 09/11] selftests/bpf: add bpf_bkup test Geliang Tang
2022-06-01  6:45 ` [PATCH mptcp-next v5 10/11] selftests/bpf: add bpf_rr scheduler Geliang Tang
2022-06-01  6:46 ` [PATCH mptcp-next v5 11/11] selftests/bpf: add bpf_rr test Geliang Tang
2022-06-01  6:57   ` selftests/bpf: add bpf_rr test: Build Failure MPTCP CI
2022-06-01  8:16   ` selftests/bpf: add bpf_rr test: Tests Results MPTCP CI

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=202206011710.y7OIrPON-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=geliang.tang@suse.com \
    --cc=kbuild-all@lists.01.org \
    --cc=mptcp@lists.linux.dev \
    /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