From: kernel test robot <lkp@intel.com>
To: steven@liquorix.net
Cc: oe-kbuild-all@lists.linux.dev
Subject: [zen:6.5/bbr3 1/1] net/ipv4/tcp_bbr.c:1315:5: warning: no previous prototype for 'bbr_ecn_cut'
Date: Tue, 29 Aug 2023 08:50:09 +0800 [thread overview]
Message-ID: <202308290834.BxWjxgec-lkp@intel.com> (raw)
tree: https://github.com/zen-kernel/zen-kernel 6.5/bbr3
head: bcb27e4adacda606c76349bfba3305db6ea83887
commit: bcb27e4adacda606c76349bfba3305db6ea83887 [1/1] bbr3-6.5: initial import
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20230829/202308290834.BxWjxgec-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230829/202308290834.BxWjxgec-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202308290834.BxWjxgec-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> net/ipv4/tcp_bbr.c:1315:5: warning: no previous prototype for 'bbr_ecn_cut' [-Wmissing-prototypes]
1315 | u32 bbr_ecn_cut(struct sock *sk)
| ^~~~~~~~~~~
>> net/ipv4/tcp_bbr.c:2036:18: warning: no previous prototype for 'bbr_main' [-Wmissing-prototypes]
2036 | __bpf_kfunc void bbr_main(struct sock *sk, const struct rate_sample *rs)
| ^~~~~~~~
net/ipv4/tcp_bbr.c: In function 'bbr_main':
>> net/ipv4/tcp_bbr.c:2042:17: warning: variable 'round_delivered' set but not used [-Wunused-but-set-variable]
2042 | u32 bw, round_delivered;
| ^~~~~~~~~~~~~~~
vim +/bbr_ecn_cut +1315 net/ipv4/tcp_bbr.c
1313
1314 /* How should we multiplicatively cut bw or inflight limits based on ECN? */
> 1315 u32 bbr_ecn_cut(struct sock *sk)
1316 {
1317 struct bbr *bbr = inet_csk_ca(sk);
1318
1319 return BBR_UNIT -
1320 ((bbr->ecn_alpha * bbr_param(sk, ecn_factor)) >> BBR_SCALE);
1321 }
1322
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-08-29 0:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202308290834.BxWjxgec-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=steven@liquorix.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.