From: kernel test robot <lkp@intel.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, davem@davemloft.net,
kuba@kernel.org, edumazet@google.com, pabeni@redhat.com,
alexander.duyck@gmail.com, fw@strlen.de,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH net-next v2 1/3] net: add skb_segment kunit test
Date: Mon, 9 Oct 2023 12:01:33 +0800 [thread overview]
Message-ID: <202310091154.3StA08FY-lkp@intel.com> (raw)
In-Reply-To: <20231008201244.3700784-2-willemdebruijn.kernel@gmail.com>
Hi Willem,
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/Willem-de-Bruijn/net-add-skb_segment-kunit-test/20231009-041424
base: net-next/main
patch link: https://lore.kernel.org/r/20231008201244.3700784-2-willemdebruijn.kernel%40gmail.com
patch subject: [PATCH net-next v2 1/3] net: add skb_segment kunit test
config: i386-randconfig-001-20231009 (https://download.01.org/0day-ci/archive/20231009/202310091154.3StA08FY-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231009/202310091154.3StA08FY-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/202310091154.3StA08FY-lkp@intel.com/
All errors (new ones prefixed by >>):
>> net/core/gso_test.c:10:32: error: initializer element is not constant
static const int payload_len = (2 * gso_size) + last_seg_size;
^
vim +10 net/core/gso_test.c
8
9 /* default: create 3 segment gso packet */
> 10 static const int payload_len = (2 * gso_size) + last_seg_size;
11
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-09 4:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 20:12 [PATCH net-next v2 0/3] add skb_segment kunit coverage Willem de Bruijn
2023-10-08 20:12 ` [PATCH net-next v2 1/3] net: add skb_segment kunit test Willem de Bruijn
2023-10-09 4:01 ` kernel test robot [this message]
2023-10-08 20:12 ` [PATCH net-next v2 2/3] net: parametrize skb_segment unit test to expand coverage Willem de Bruijn
2023-10-08 20:12 ` [PATCH net-next v2 3/3] net: expand skb_segment unit test with frag_list coverage Willem de Bruijn
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=202310091154.3StA08FY-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexander.duyck@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.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).