Netdev List
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Sudarsana Kalluru <Sudarsana.Kalluru@cavium.com>
Cc: kbuild-all@01.org, davem@davemloft.net, netdev@vger.kernel.org,
	Yuval.Mintz@cavium.com,
	Sudarsana Reddy Kalluru <sudarsana.kalluru@cavium.com>
Subject: Re: [PATCH net-next 1/2] qed: Add infrastructure for PTP support.
Date: Sat, 28 Jan 2017 13:37:50 +0800	[thread overview]
Message-ID: <201701281338.YjgWUQue%fengguang.wu@intel.com> (raw)
In-Reply-To: <1485531020-8905-2-git-send-email-Sudarsana.Kalluru@cavium.com>

[-- Attachment #1: Type: text/plain, Size: 824 bytes --]

Hi Sudarsana,

[auto build test ERROR on net-next/master]

url:    https://github.com/0day-ci/linux/commits/Sudarsana-Kalluru/qed-Add-infrastructure-for-PTP-support/20170127-233853
config: i386-randconfig-c0-01281020 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   drivers/built-in.o: In function `qed_ptp_hw_adjfreq':
>> qed_ptp.c:(.text+0x19f3c3): undefined reference to `__divdi3'
   qed_ptp.c:(.text+0x19f45a): undefined reference to `__divdi3'
   qed_ptp.c:(.text+0x19f498): undefined reference to `__divdi3'

---
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: 34418 bytes --]

  parent reply	other threads:[~2017-01-28  5:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-27 15:30 [PATCH net-next 0/2] qed*: Add support for PTP Sudarsana Kalluru
2017-01-27 15:30 ` [PATCH net-next 1/2] qed: Add infrastructure for PTP support Sudarsana Kalluru
2017-01-28  1:48   ` kbuild test robot
2017-01-28  5:37   ` kbuild test robot [this message]
2017-01-27 15:30 ` [PATCH net-next 2/2] qede: Add driver support for PTP Sudarsana Kalluru

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=201701281338.YjgWUQue%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=Sudarsana.Kalluru@cavium.com \
    --cc=Yuval.Mintz@cavium.com \
    --cc=davem@davemloft.net \
    --cc=kbuild-all@01.org \
    --cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox