From: kbuild test robot <lkp@intel.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, Eric Dumazet <eric.dumazet@gmail.com>,
nick <xerofoify@gmail.com>,
netdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Ye Xiaolong <xiaolong.ye@intel.com>,
intel-wired-lan@lists.osuosl.org,
Satyam Sharma <satyam@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
cc@osuosl.org
Subject: Re: [PATCH] schedule function called for e1000 driver interrupt
Date: Tue, 26 Jul 2016 17:45:53 +0800 [thread overview]
Message-ID: <201607261708.iNApqj7w%fengguang.wu@intel.com> (raw)
In-Reply-To: <20160726093224.GA10339@wfg-t540p.sh.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]
Hi,
[auto build test ERROR on jkirsher-next-queue/dev-queue]
[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/Fengguang-Wu/schedule-function-called-for-e1000-driver-interrupt/20160726-173521
base: https://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue.git dev-queue
config: x86_64-randconfig-x011-201630 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/net/ethernet/intel/e1000/e1000_main.c: In function 'e1000_intr':
>> drivers/net/ethernet/intel/e1000/e1000_main.c:3800:22: error: 'struct e1000_adapter' has no member named 'watchdog_timer'; did you mean 'watchdog_task'?
mod_timer(&adapter->watchdog_timer, jiffies + 1);
^~
vim +3800 drivers/net/ethernet/intel/e1000/e1000_main.c
3794 return IRQ_HANDLED;
3795
3796 if (unlikely(icr & (E1000_ICR_RXSEQ | E1000_ICR_LSC))) {
3797 hw->get_link_status = 1;
3798 /* guard against interrupt when we're going down */
3799 if (!test_bit(__E1000_DOWN, &adapter->flags))
> 3800 mod_timer(&adapter->watchdog_timer, jiffies + 1);
3801 }
3802
3803 /* disable interrupts, without the synchronize_irq bit */
---
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: 26488 bytes --]
next prev parent reply other threads:[~2016-07-26 9:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 3:50 [e1000_netpoll] BUG: sleeping function called from invalid context at kernel/irq/manage.c:110 Fengguang Wu
2016-07-26 9:14 ` Eric Dumazet
[not found] ` <20160726093224.GA10339@wfg-t540p.sh.intel.com>
2016-07-26 9:45 ` kbuild test robot [this message]
2016-07-26 9:50 ` Thomas Gleixner
[not found] ` <8578bb16-cd04-e8a5-c7f4-be061ede95b4@gmail.com>
2016-07-28 7:45 ` Thomas Gleixner
2016-07-28 9:46 ` Valdis.Kletnieks
2016-07-26 9:50 ` [PATCH] schedule function called for e1000 driver interrupt kbuild test robot
2016-07-26 15:32 ` [e1000_netpoll] BUG: sleeping function called from invalid context at kernel/irq/manage.c:110 Fengguang Wu
2016-07-26 16:28 ` Eric Dumazet
2016-07-27 15:01 ` Fengguang Wu
2016-07-27 18:50 ` Eric Dumazet
2016-07-27 21:38 ` Jeff Kirsher
2016-07-28 5:43 ` Eric Dumazet
2016-07-28 10:19 ` Sabrina Dubroca
2016-07-28 12:21 ` Thomas Gleixner
2016-07-28 13:30 ` Fengguang Wu
2016-07-28 23:28 ` [Intel-wired-lan] " Francois Romieu
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=201607261708.iNApqj7w%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=cc@osuosl.org \
--cc=eric.dumazet@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=satyam@infradead.org \
--cc=tglx@linutronix.de \
--cc=xerofoify@gmail.com \
--cc=xiaolong.ye@intel.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;
as well as URLs for NNTP newsgroup(s).