From: kbuild test robot <lkp@intel.com>
To: Bryan Whitehead <Bryan.Whitehead@microchip.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org
Subject: [net-next:master 540/547] drivers/net/ethernet/microchip/lan743x_ethtool.c:558:18: error: 'struct lan743x_ptp' has no member named 'ptp_clock'; did you mean 'tx_ts_lock'?
Date: Sun, 12 Aug 2018 06:18:51 +0800 [thread overview]
Message-ID: <201808120647.ptNSgiZO%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3064 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
head: 9a95d9c6429bb58905fdfc95da2e1b7cc3fb55b7
commit: 07624df1c9efd4b7f2f6762581587c590b03c7a2 [540/547] lan743x: lan743x: Add PTP support
config: x86_64-randconfig-ne0-08120429 (attached as .config)
compiler: gcc-6 (Debian 6.4.0-9) 6.4.0 20171026
reproduce:
git checkout 07624df1c9efd4b7f2f6762581587c590b03c7a2
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/net/ethernet/microchip/lan743x_ethtool.c: In function 'lan743x_ethtool_get_ts_info':
>> drivers/net/ethernet/microchip/lan743x_ethtool.c:558:18: error: 'struct lan743x_ptp' has no member named 'ptp_clock'; did you mean 'tx_ts_lock'?
if (adapter->ptp.ptp_clock)
^
drivers/net/ethernet/microchip/lan743x_ethtool.c:559:52: error: 'struct lan743x_ptp' has no member named 'ptp_clock'; did you mean 'tx_ts_lock'?
ts_info->phc_index = ptp_clock_index(adapter->ptp.ptp_clock);
^
--
drivers/net/ethernet/microchip/lan743x_ptp.c: In function 'lan743x_ptp_isr':
>> drivers/net/ethernet/microchip/lan743x_ptp.c:781:26: error: 'struct lan743x_ptp' has no member named 'ptp_clock'; did you mean 'tx_ts_lock'?
ptp_schedule_worker(ptp->ptp_clock, 0);
^~
drivers/net/ethernet/microchip/lan743x_ptp.c: In function 'lan743x_ptp_open':
drivers/net/ethernet/microchip/lan743x_ptp.c:879:6: warning: unused variable 'ret' [-Wunused-variable]
int ret = -ENODEV;
^~~
At top level:
drivers/net/ethernet/microchip/lan743x_ptp.c:63:13: warning: 'lan743x_ptp_tx_ts_enqueue_ts' defined but not used [-Wunused-function]
static void lan743x_ptp_tx_ts_enqueue_ts(struct lan743x_adapter *adapter,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +558 drivers/net/ethernet/microchip/lan743x_ethtool.c
545
546 static int lan743x_ethtool_get_ts_info(struct net_device *netdev,
547 struct ethtool_ts_info *ts_info)
548 {
549 struct lan743x_adapter *adapter = netdev_priv(netdev);
550
551 ts_info->so_timestamping = SOF_TIMESTAMPING_TX_SOFTWARE |
552 SOF_TIMESTAMPING_RX_SOFTWARE |
553 SOF_TIMESTAMPING_SOFTWARE |
554 SOF_TIMESTAMPING_TX_HARDWARE |
555 SOF_TIMESTAMPING_RX_HARDWARE |
556 SOF_TIMESTAMPING_RAW_HARDWARE;
557
> 558 if (adapter->ptp.ptp_clock)
559 ts_info->phc_index = ptp_clock_index(adapter->ptp.ptp_clock);
560 else
561 ts_info->phc_index = -1;
562
563 ts_info->tx_types = BIT(HWTSTAMP_TX_OFF) |
564 BIT(HWTSTAMP_TX_ON) |
565 BIT(HWTSTAMP_TX_ONESTEP_SYNC);
566 ts_info->rx_filters = BIT(HWTSTAMP_FILTER_NONE) |
567 BIT(HWTSTAMP_FILTER_ALL);
568 return 0;
569 }
570
---
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: 29434 bytes --]
reply other threads:[~2018-08-12 0:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201808120647.ptNSgiZO%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=Bryan.Whitehead@microchip.com \
--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