From: kbuild test robot <lkp@intel.com>
To: Kshitiz Gupta <kshitiz.gupta@ni.com>
Cc: kbuild-all@01.org, Aaron Brown <aaron.f.brown@intel.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Nathan Sullivan <nathan.sullivan@ni.com>,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Kshitiz Gupta <kshitiz.gupta@ni.com>
Subject: Re: [PATCH] igb: fix adjusting ptp timestamps for tx/rx latency
Date: Sat, 16 Jul 2016 06:55:39 +0800 [thread overview]
Message-ID: <201607160644.Q6MtmLkD%fengguang.wu@intel.com> (raw)
In-Reply-To: <1468620496-7849-1-git-send-email-kshitiz.gupta@ni.com>
[-- Attachment #1: Type: text/plain, Size: 2310 bytes --]
Hi,
[auto build test ERROR on jkirsher-next-queue/dev-queue]
[also build test ERROR on v4.7-rc7 next-20160715]
[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/Kshitiz-Gupta/igb-fix-adjusting-ptp-timestamps-for-tx-rx-latency/20160716-062544
base: https://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue.git dev-queue
config: sparc64-allyesconfig (attached as .config)
compiler: sparc64-linux-gnu-gcc (Debian 5.3.1-8) 5.3.1 20160205
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=sparc64
All errors (new ones prefixed by >>):
drivers/net/ethernet/intel/igb/igb_ptp.c: In function 'igb_ptp_rx_pktstamp':
>> drivers/net/ethernet/intel/igb/igb_ptp.c:783:12: error: 'IGB_RX_LATENCY_10' undeclared (first use in this function)
adjust = IGB_RX_LATENCY_10;
^
drivers/net/ethernet/intel/igb/igb_ptp.c:783:12: note: each undeclared identifier is reported only once for each function it appears in
>> drivers/net/ethernet/intel/igb/igb_ptp.c:786:12: error: 'IGB_RX_LATENCY_100' undeclared (first use in this function)
adjust = IGB_RX_LATENCY_100;
^
>> drivers/net/ethernet/intel/igb/igb_ptp.c:789:12: error: 'IGB_RX_LATENCY_1000' undeclared (first use in this function)
adjust = IGB_RX_LATENCY_1000;
^
vim +/IGB_RX_LATENCY_10 +783 drivers/net/ethernet/intel/igb/igb_ptp.c
777 igb_ptp_systim_to_hwtstamp(adapter, skb_hwtstamps(skb),
778 le64_to_cpu(regval[1]));
779
780 /* adjust timestamp for the RX latency based on link speed */
781 switch (adapter->link_speed) {
782 case SPEED_10:
> 783 adjust = IGB_RX_LATENCY_10;
784 break;
785 case SPEED_100:
> 786 adjust = IGB_RX_LATENCY_100;
787 break;
788 case SPEED_1000:
> 789 adjust = IGB_RX_LATENCY_1000;
790 break;
791 }
792 skb_hwtstamps(skb)->hwtstamp =
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 46471 bytes --]
prev parent reply other threads:[~2016-07-15 22:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 22:08 [PATCH] igb: fix adjusting ptp timestamps for tx/rx latency Kshitiz Gupta
2016-07-15 22:55 ` 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=201607160644.Q6MtmLkD%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=aaron.f.brown@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=kbuild-all@01.org \
--cc=kshitiz.gupta@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan.sullivan@ni.com \
--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;
as well as URLs for NNTP newsgroup(s).