From: kbuild test robot <lkp@intel.com>
To: mohamedalrshah <mohamed.a.alrshah@ieee.org>
Cc: kbuild-all@01.org, davem@davemloft.net, netdev@vger.kernel.org,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
"Mohamed A . Alrshah" <mohamed.a.alrshah@ieee.org>,
Mohamed Othman <mothman@upm.edu.my>,
Borhanuddin Ali <borhan@upm.edu.my>,
Zurina Hanapi <zurinamh@upm.edu.my>
Subject: Re: [PATCH] Adding-Agile-SD-TCP-module-and-modifying-Kconfig-and-makefile
Date: Thu, 17 Aug 2017 08:12:26 +0800 [thread overview]
Message-ID: <201708170813.rVOSFUfk%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170815130806.25168-1-mohamed.a.alrshah@ieee.org>
[-- Attachment #1: Type: text/plain, Size: 2250 bytes --]
Hi mohamedalrshah,
[auto build test ERROR on net/master]
[also build test ERROR on v4.13-rc5 next-20170816]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/mohamedalrshah/Adding-Agile-SD-TCP-module-and-modifying-Kconfig-and-makefile/20170817-055643
config: i386-allyesconfig (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
>> net//ipv4/tcp_agilesd.c:35:15: error: expected identifier before numeric constant
enum dystate{SS=0, CA=1} agilesd_tcp_status;
^~
net//ipv4/tcp_agilesd.c: In function 'agilesdtcp_cong_avoid':
net//ipv4/tcp_agilesd.c:87:28: error: 'CA' undeclared (first use in this function)
ca->agilesd_tcp_status = CA;
^~
net//ipv4/tcp_agilesd.c:87:28: note: each undeclared identifier is reported only once for each function it appears in
net//ipv4/tcp_agilesd.c: In function 'agilesdtcp_recalc_ssthresh':
net//ipv4/tcp_agilesd.c:121:32: error: 'CA' undeclared (first use in this function)
if (ca->agilesd_tcp_status == CA)
^~
net//ipv4/tcp_agilesd.c: At top level:
net//ipv4/tcp_agilesd.c:169:16: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
.pkts_acked = agilesdtcp_acked,
^~~~~~~~~~~~~~~~
net//ipv4/tcp_agilesd.c:169:16: note: (near initialization for 'agilesdtcp.pkts_acked')
cc1: some warnings being treated as errors
vim +35 net//ipv4/tcp_agilesd.c
29
30 /* Agile-SD Parameters */
31 struct agilesdtcp {
32 u32 loss_cwnd; /* congestion window at last loss.*/
33 u32 frac_tracer; /* This is to trace the fractions of the increment.*/
34 u32 degraded_loss_cwnd; /* loss_cwnd after degradation.*/
> 35 enum dystate{SS=0, CA=1} agilesd_tcp_status;
36 };
37
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 60442 bytes --]
prev parent reply other threads:[~2017-08-17 0:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 13:08 mohamedalrshah
2017-08-15 13:51 ` Neal Cardwell
2017-08-15 16:41 ` Randy Dunlap
2017-08-15 17:36 ` David Miller
2017-08-15 17:50 ` Randy Dunlap
2017-08-15 14:01 ` Neal Cardwell
2017-08-15 17:10 ` Randy Dunlap
2017-08-16 23:36 ` kbuild test robot
2017-08-17 0:12 ` kbuild test robot [this message]
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=201708170813.rVOSFUfk%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=borhan@upm.edu.my \
--cc=davem@davemloft.net \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mohamed.a.alrshah@ieee.org \
--cc=mothman@upm.edu.my \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=zurinamh@upm.edu.my \
/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
all inboxes | Powered by JetHome®