From: kbuild test robot <lkp@intel.com>
To: Vaibhav Kothari <vaibhavddit@gmail.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Vaibhav Kothari <vaibhavddit@gmail.com>
Subject: Re: [PATCH] staging: irda: net: Fix warning for incomplete Declarations in irlap.c
Date: Sat, 30 Dec 2017 06:36:13 +0800 [thread overview]
Message-ID: <201712300632.iL6DwKvK%fengguang.wu@intel.com> (raw)
In-Reply-To: <1514448041-26200-1-git-send-email-vaibhavddit@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
Hi Vaibhav,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.15-rc5 next-20171222]
[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/Vaibhav-Kothari/staging-irda-net-Fix-warning-for-incomplete-Declarations-in-irlap-c/20171230-023604
config: x86_64-allyesdebian (attached as .config)
compiler: gcc-7 (Debian 7.2.0-12) 7.2.1 20171025
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/staging/irda/net/timer.o: In function `irlap_start_query_timer':
timer.c:(.text+0xcb): undefined reference to `sysctl_slot_timeout'
>> drivers/staging/irda/net/irsysctl.o:(.data+0x148): undefined reference to `sysctl_slot_timeout'
>> drivers/staging/irda/net/irsysctl.o:(.data+0x2c8): undefined reference to `sysctl_warn_noreply_time'
---
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: 39849 bytes --]
prev parent reply other threads:[~2017-12-29 22:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 8:00 Vaibhav Kothari
2017-12-29 22:01 ` kbuild test robot
2017-12-29 22:36 ` 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=201712300632.iL6DwKvK%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vaibhavddit@gmail.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®