All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>,
	Daniel Baluta <daniel.baluta@intel.com>,
	kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, Jonathan Cameron <jic23@kernel.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	Hartmut Knaack <knaack.h@gmx.de>
Subject: Re: [iio:togreg 11/13] industrialio-sw-trigger.c:undefined reference to `iio_configfs_subsys'
Date: Thu, 03 Dec 2015 19:34:16 +0100	[thread overview]
Message-ID: <56608B28.1040808@metafoo.de> (raw)
In-Reply-To: <56608782.7000205@jic23.retrosnub.co.uk>

On 12/03/2015 07:18 PM, Jonathan Cameron wrote:
> On 03/12/15 16:07, Daniel Baluta wrote:
>> I see, strange. It shouldn't complain about it, because it is immediately exported.
>>
>> I will have a closer look.
> Indeed, it's clearly BS (serves me right for fly by sparse fixing during
> applying patches:).  Looking at the moment like a bug in Sparse which is 
> unusual...
> 
> cc'd the list as maybe someone else will be able to suggest what is going on here.


sparse complains if there is no forward declaration in a header file. This
could either mean there is non or the header file is not included in the C
file where it is defined.

>>
>>
>> struct configfs_subsystem iio_configfs_subsys = {
>> »       .su_group = {
>> »       »       .cg_item = {
>> »       »       »       .ci_namebuf = "iio",
>> »       »       »       .ci_type = &iio_root_group_type,
>> »       »       },
>> »       },
>> »       .su_mutex = __MUTEX_INITIALIZER(iio_configfs_subsys.su_mutex),
>> };
>> EXPORT_SYMBOL(iio_configfs_subsys);
>>
>>
>>        
>>
>> On 12/03/2015 05:53 PM, Jonathan Cameron wrote:
>>> Classic symbol not exported should it be static from sparse.
>>>
>>> On 3 December 2015 08:57:25 GMT+00:00, Daniel Baluta
>>> <daniel.baluta@intel.com> wrote:
>>>
>>>     Ooops, yes!
>>>
>>>     Sorry for the late answer, Jonathan :(.
>>>
>>>     What was the warning you got and fixed with adding static?
>>>
>>>     thanks,
>>>     Daniel
>>>
>>>     On 12/03/2015 08:41 AM, Jonathan Cameron wrote:
>>>
>>>         I'll back that static addition out then!
>>>
>>>         On 2 December 2015 23:23:27 GMT+00:00, kbuild test robot
>>>         <fengguang.wu@intel.com> wrote:
>>>
>>>         tree:https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
>>>         togreg
>>>         head: 5a9776becbe3a15f0616883244142b3e6addf93b
>>>         commit: 13bbe76b0b58c958ea6b9fcb982ca5f969f89d48 [11/13] iio:
>>>         core: Introduce IIO software triggers
>>>         config: i386-allyesconfig (attached as .config)
>>>         reproduce:
>>>         git checkout 13bbe76b0b58c958ea6b9fcb982ca5f969f89d48
>>>         # save the attached .config to linux build tree
>>>         make ARCH=i386
>>>
>>>         All errors (new ones prefixed by >>):
>>>
>>>         drivers/built-in.o: In function `iio_sw_trigger_init':
>>>
>>>         industrialio-sw-trigger.c:(.init.text+0x801d0): undefined
>>>         reference to `iio_configfs_subsys'
>>>
>>>
>>>         ---
>>>         0-DAY kernel test infrastructure Open Source Technology Center
>>>         https://lists.01.org/pipermail/kbuild-all Intel Corporation
>>>
>>>
>>>         --
>>>         Sent from my Android device with K-9 Mail. Please excuse my brevity.
>>>
>>>
>>> -- 
>>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
> 


  reply	other threads:[~2015-12-03 18:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201512030723.5UzAF24I%fengguang.wu@intel.com>
     [not found] ` <43E08F24-AB64-4F2B-B422-3425A2D4D182@jic23.retrosnub.co.uk>
     [not found]   ` <566003F5.5090001@intel.com>
     [not found]     ` <D645C15C-AF9D-47B3-A254-9D6137CCAD69@jic23.retrosnub.co.uk>
     [not found]       ` <566068B7.5090408@intel.com>
2015-12-03 18:18         ` [iio:togreg 11/13] industrialio-sw-trigger.c:undefined reference to `iio_configfs_subsys' Jonathan Cameron
2015-12-03 18:34           ` Lars-Peter Clausen [this message]
2015-12-05 16:31             ` Jonathan Cameron

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=56608B28.1040808@metafoo.de \
    --to=lars@metafoo.de \
    --cc=daniel.baluta@intel.com \
    --cc=fengguang.wu@intel.com \
    --cc=jic23@jic23.retrosnub.co.uk \
    --cc=jic23@kernel.org \
    --cc=kbuild-all@01.org \
    --cc=knaack.h@gmx.de \
    --cc=linux-iio@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 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.