From: kbuild test robot <lkp@intel.com>
To: Eduardo Otubo <otubo@redhat.com>
Cc: kbuild-all@01.org, xen-devel@lists.xenproject.org,
netdev@vger.kernel.org, paul.durrant@citrix.com,
wei.liu2@citrix.com, linux-kernel@vger.kernel.org,
vkuznets@redhat.com, cavery@redhat.com, cheshi@redhat.com,
mgamal@redhat.com, Eduardo Otubo <otubo@redhat.com>
Subject: Re: [PATCH] xen-netfront: remove warning when unloading module
Date: Wed, 22 Nov 2017 19:44:49 +0800 [thread overview]
Message-ID: <201711221820.4HONikRo%fengguang.wu@intel.com> (raw)
In-Reply-To: <20171120104109.11585-1-otubo@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1946 bytes --]
Hi Eduardo,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on xen-tip/linux-next]
[also build test ERROR on v4.14 next-20171121]
[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/Eduardo-Otubo/xen-netfront-remove-warning-when-unloading-module/20171122-163844
base: https://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git linux-next
config: x86_64-allmodconfig (attached as .config)
compiler: gcc-6 (Debian 6.4.0-9) 6.4.0 20171026
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers//net/xen-netfront.c: In function 'xennet_remove':
>> drivers//net/xen-netfront.c:2139:12: error: 'struct xenbus_device' has no member named 'xenbus_state'
while (dev->xenbus_state != XenbusStateClosed){
^~
vim +2139 drivers//net/xen-netfront.c
2126
2127 static int xennet_remove(struct xenbus_device *dev)
2128 {
2129 struct netfront_info *info = dev_get_drvdata(&dev->dev);
2130
2131 dev_dbg(&dev->dev, "%s\n", dev->nodename);
2132
2133 xenbus_switch_state(dev, XenbusStateClosing);
2134 while (xenbus_read_driver_state(dev->otherend) != XenbusStateClosing){
2135 cpu_relax();
2136 schedule();
2137 }
2138 xenbus_switch_state(dev, XenbusStateClosed);
> 2139 while (dev->xenbus_state != XenbusStateClosed){
2140 cpu_relax();
2141 schedule();
2142 }
2143
2144 xennet_disconnect_backend(info);
2145
2146 unregister_netdev(info->netdev);
2147
2148 if (info->queues)
2149 xennet_destroy_queues(info);
2150 xennet_free_netdev(info->netdev);
2151
2152 return 0;
2153 }
2154
---
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: 61719 bytes --]
next prev parent reply other threads:[~2017-11-22 11:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 10:41 [PATCH] xen-netfront: remove warning when unloading module Eduardo Otubo
2017-11-20 10:49 ` Wei Liu
2017-11-20 11:17 ` Juergen Gross
2017-11-20 11:17 ` Juergen Gross
2017-11-20 12:59 ` Eduardo Otubo
2017-11-20 12:59 ` Eduardo Otubo
2017-11-20 10:49 ` Wei Liu
2017-11-20 10:55 ` Paul Durrant
2017-11-20 10:55 ` Paul Durrant
2017-11-20 12:56 ` 'Eduardo Otubo'
2017-11-20 12:56 ` 'Eduardo Otubo'
2017-11-22 11:44 ` kbuild test robot [this message]
2017-11-22 11:44 ` kbuild test robot
-- strict thread matches above, loose matches on Subject: below --
2017-11-20 10:41 Eduardo Otubo
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=201711221820.4HONikRo%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=cavery@redhat.com \
--cc=cheshi@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgamal@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=otubo@redhat.com \
--cc=paul.durrant@citrix.com \
--cc=vkuznets@redhat.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.