From: kbuild test robot <lkp@intel.com>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: kbuild-all@01.org, "David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Stefan Wahren <stefan.wahren@i2se.com>
Subject: Re: [PATCH net-next 8/8] net: qualcomm: add QCA7000 UART driver
Date: Tue, 20 Sep 2016 22:44:57 +0800 [thread overview]
Message-ID: <201609202253.jYnEZtwg%fengguang.wu@intel.com> (raw)
In-Reply-To: <1474376544-20515-9-git-send-email-stefan.wahren@i2se.com>
[-- Attachment #1: Type: text/plain, Size: 1538 bytes --]
Hi Stefan,
[auto build test ERROR on net-next/master]
url: https://github.com/0day-ci/linux/commits/Stefan-Wahren/net-qualcomm-add-QCA7000-UART-driver/20160920-210908
config: i386-allmodconfig (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
drivers/net/ethernet/qualcomm/qca_uart.c: In function 'qcauart_netdev_xmit':
>> drivers/net/ethernet/qualcomm/qca_uart.c:302:5: error: 'struct net_device' has no member named 'trans_start'; did you mean 'mem_start'?
dev->trans_start = jiffies;
^~
drivers/net/ethernet/qualcomm/qca_uart.c: In function 'qcauart_netdev_tx_timeout':
drivers/net/ethernet/qualcomm/qca_uart.c:314:29: error: 'struct net_device' has no member named 'trans_start'; did you mean 'mem_start'?
jiffies, jiffies - dev->trans_start);
^~
vim +302 drivers/net/ethernet/qualcomm/qca_uart.c
296 written = qca->tty->ops->write(qca->tty, qca->xbuff, pos - qca->xbuff);
297 qca->xleft = (pos - qca->xbuff) - written;
298 qca->xhead = qca->xbuff + written;
299 n_stats->tx_bytes += written;
300 spin_unlock(&qca->lock);
301
> 302 dev->trans_start = jiffies;
303 out:
304 kfree_skb(skb);
305 return NETDEV_TX_OK;
---
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: 55965 bytes --]
next prev parent reply other threads:[~2016-09-20 14:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 13:02 [PATCH net-next 0/8] " Stefan Wahren
2016-09-20 13:02 ` [PATCH net-next 1/8] net: qualcomm: remove unnecessary includes Stefan Wahren
2016-09-20 13:02 ` [PATCH net-next 2/8] net: qca_debug: use net_device_ops instead of direct call Stefan Wahren
2016-09-20 13:02 ` [PATCH net-next 3/8] net: qualcomm: move qcaspi_tx_cmd to qca_spi.c Stefan Wahren
2016-09-20 13:02 ` [PATCH net-next 4/8] net: qualcomm: rename qca_framing.c to qca_common.c Stefan Wahren
2016-09-20 13:02 ` [PATCH net-next 5/8] net: qualcomm: move MTU handling to qca_common Stefan Wahren
2016-09-20 13:02 ` [PATCH net-next 6/8] net: qualcomm: prepare frame decoding for UART driver Stefan Wahren
2016-09-20 13:02 ` [PATCH net-next 7/8] net: qualcomm: make qca_common a separate kernel module Stefan Wahren
2016-09-20 13:02 ` [PATCH net-next 8/8] net: qualcomm: add QCA7000 UART driver Stefan Wahren
2016-09-20 14:44 ` kbuild test robot [this message]
2016-09-20 16:43 ` Stefan Wahren
2016-09-20 15:32 ` Marcel Holtmann
2016-09-21 7:49 ` Stefan Wahren
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=201609202253.jYnEZtwg%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stefan.wahren@i2se.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
all inboxes | Powered by JetHome®