mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Daeseok Youn <daeseok.youn@gmail.com>
Cc: kbuild-all@01.org, lidza.louina@gmail.com,
	devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
	driverdev-devel@linuxdriverproject.org,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: dgnc: fix CamelCase in dgnc_driver.c
Date: Wed, 23 Mar 2016 16:28:41 +0800	[thread overview]
Message-ID: <201603231601.LbhTLV0C%fengguang.wu@intel.com> (raw)
In-Reply-To: <20160323051359.GA4812@SEL-JYOUN-D1>

[-- Attachment #1: Type: text/plain, Size: 1520 bytes --]

Hi Daeseok,

[auto build test ERROR on staging/staging-testing]
[also build test ERROR on next-20160323]
[cannot apply to v4.5]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]

url:    https://github.com/0day-ci/linux/commits/Daeseok-Youn/staging-dgnc-fix-CamelCase-in-dgnc_driver-c/20160323-131708
config: x86_64-randconfig-s1-03231424 (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   drivers/built-in.o: In function `dgnc_mgmt_ioctl':
>> (.text+0x7ca676): undefined reference to `dgnc_NumBoards'
   drivers/built-in.o: In function `dgnc_mgmt_ioctl':
   (.text+0x7ca71d): undefined reference to `dgnc_NumBoards'
   drivers/built-in.o: In function `dgnc_mgmt_ioctl':
>> (.text+0x7ca73e): undefined reference to `dgnc_Board'
   drivers/built-in.o: In function `dgnc_mgmt_ioctl':
   (.text+0x7ca759): undefined reference to `dgnc_Board'
   drivers/built-in.o: In function `dgnc_mgmt_ioctl':
   (.text+0x7ca83a): undefined reference to `dgnc_NumBoards'
   drivers/built-in.o: In function `dgnc_mgmt_ioctl':
   (.text+0x7ca85c): undefined reference to `dgnc_Board'
   drivers/built-in.o: In function `dgnc_driver_boards_show':
>> dgnc_sysfs.c:(.text+0x7d2bda): undefined reference to `dgnc_NumBoards'

---
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: 21874 bytes --]

      reply	other threads:[~2016-03-23  8:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-23  5:13 Daeseok Youn
2016-03-23  8:28 ` 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=201603231601.LbhTLV0C%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=daeseok.youn@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kbuild-all@01.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=lidza.louina@gmail.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®