From: kbuild test robot <lkp@intel.com>
To: Andy Zhou <azhou@ovn.org>
Cc: kbuild-all@01.org, netdev@vger.kernel.org, pshelar@ovn.org,
joe@ovn.org, gvrose8192@gmail.com, Andy Zhou <azhou@ovn.org>
Subject: Re: [net-next v3 3/4] openvswitch: Add meter infrastructure
Date: Wed, 8 Nov 2017 13:30:26 +0800 [thread overview]
Message-ID: <201711081331.GNbAEsJN%fengguang.wu@intel.com> (raw)
In-Reply-To: <1509957021-10795-4-git-send-email-azhou@ovn.org>
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
Hi Andy,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on net-next/master]
url: https://github.com/0day-ci/linux/commits/Andy-Zhou/Openvswitch-meter-action/20171108-053451
config: i386-randconfig-i0-201745 (attached as .config)
compiler: gcc-4.8 (Debian 4.8.4-1) 4.8.4
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
net/openvswitch/meter.o: In function `ovs_meter_cmd_set':
>> meter.c:(.text+0x8b4): undefined reference to `__udivdi3'
net/openvswitch/meter.o: In function `ovs_meter_execute':
meter.c:(.text+0xeb0): undefined reference to `__udivdi3'
---
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: 29557 bytes --]
next prev parent reply other threads:[~2017-11-08 5:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 8:30 [net-next v3 0/4] Openvswitch meter action Andy Zhou
2017-11-06 8:30 ` [net-next v3 1/4] openvswitch: Add meter netlink definitions Andy Zhou
2017-11-06 8:30 ` [net-next v3 2/4] openvswitch: export get_dp() API Andy Zhou
2017-11-06 8:30 ` [net-next v3 3/4] openvswitch: Add meter infrastructure Andy Zhou
2017-11-08 1:59 ` kbuild test robot
2017-11-08 5:30 ` kbuild test robot [this message]
2017-11-06 8:30 ` [net-next v3 4/4] openvswitch: Add meter action support Andy Zhou
2017-11-06 12:04 ` [net-next v3 0/4] Openvswitch meter action Pravin Shelar
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=201711081331.GNbAEsJN%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=azhou@ovn.org \
--cc=gvrose8192@gmail.com \
--cc=joe@ovn.org \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.org \
--cc=pshelar@ovn.org \
/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.