From: kernel test robot <lkp@intel.com>
To: Subash Abhinov Kasiviswanathan <quic_subashab@quicinc.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
Subash Abhinov Kasiviswanathan <quic_subashab@quicinc.com>,
Sean Tranchetti <quic_stranche@quicinc.com>
Subject: Re: [PATCH net-next] net: qualcomm: rmnet: Add side band flow control support
Date: Sun, 24 Sep 2023 03:46:45 +0800 [thread overview]
Message-ID: <202309240339.EjUjVM7v-lkp@intel.com> (raw)
In-Reply-To: <20230920003337.1317132-1-quic_subashab@quicinc.com>
Hi Subash,
kernel test robot noticed the following build errors:
[auto build test ERROR on net-next/main]
url: https://github.com/intel-lab-lkp/linux/commits/Subash-Abhinov-Kasiviswanathan/net-qualcomm-rmnet-Add-side-band-flow-control-support/20230920-083445
base: net-next/main
patch link: https://lore.kernel.org/r/20230920003337.1317132-1-quic_subashab%40quicinc.com
patch subject: [PATCH net-next] net: qualcomm: rmnet: Add side band flow control support
config: i386-randconfig-016-20230923 (https://download.01.org/0day-ci/archive/20230924/202309240339.EjUjVM7v-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230924/202309240339.EjUjVM7v-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/202309240339.EjUjVM7v-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from usr/include/linux/netdevice.h:32,
from ./usr/include/linux/if_arp.h:27,
from <command-line>:
>> usr/include/linux/if_link.h:1389:9: error: unknown type name 'u8'
1389 | u8 operation;
| ^~
usr/include/linux/if_link.h:1390:9: error: unknown type name 'u8'
1390 | u8 txqueue;
| ^~
>> usr/include/linux/if_link.h:1391:9: error: unknown type name 'u16'
1391 | u16 padding;
| ^~~
>> usr/include/linux/if_link.h:1392:9: error: unknown type name 'u32'
1392 | u32 mark;
| ^~~
--
In file included from <command-line>:
>> ./usr/include/linux/if_link.h:1389:9: error: unknown type name 'u8'
1389 | u8 operation;
| ^~
./usr/include/linux/if_link.h:1390:9: error: unknown type name 'u8'
1390 | u8 txqueue;
| ^~
>> ./usr/include/linux/if_link.h:1391:9: error: unknown type name 'u16'
1391 | u16 padding;
| ^~~
>> ./usr/include/linux/if_link.h:1392:9: error: unknown type name 'u32'
1392 | u32 mark;
| ^~~
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-09-23 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 0:33 [PATCH net-next] net: qualcomm: rmnet: Add side band flow control support Subash Abhinov Kasiviswanathan
2023-09-21 10:51 ` Vadim Fedorenko
2023-09-21 15:38 ` Subash Abhinov Kasiviswanathan (KS)
2023-09-23 19:46 ` kernel 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=202309240339.EjUjVM7v-lkp@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=quic_stranche@quicinc.com \
--cc=quic_subashab@quicinc.com \
/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).