linux-kernel - Re: [grant:gpio/next 10/16] gpiolib.c:undefined reference to `gpiod

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5117A904.4040309@nvidia.com>
Date:	Sun, 10 Feb 2013 23:04:52 +0900
From:	Alex Courbot <acourbot@...dia.com>
To:	Grant Likely <grant.likely@...retlab.ca>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	<gnurou@...il.com>
Subject: Re: [grant:gpio/next 10/16] gpiolib.c:undefined reference to `gpiod_unexport'

Hi Grant,

On 02/10/2013 01:34 AM, Grant Likely wrote:
 > Alex, this is broken when the sysfs interface isn't enabled. Can you
 > send a fixup patch?
 >
 > g.
 >
 > On Sat, Feb 9, 2013 at 3:41 PM, kbuild test robot
 > <fengguang.wu@...el.com> wrote:
 >> tree:   git://git.secretlab.ca/git/linux-2.6.git gpio/next
 >> head:   8a307b35962e42de0f998c6029e8851c61eadb4e
 >> commit: 5bb47609e8167d733786cb781ada29536385635c [10/16] gpiolib: 
use descriptors internally
 >> config: i386-randconfig-b040 (attached as .config)
 >>
 >> All error/warnings:
 >>
 >>     drivers/built-in.o: In function `gpiod_free':
 >>>> gpiolib.c:(.text+0xda3): undefined reference to `gpiod_unexport'
 >>     drivers/built-in.o: In function `gpio_request_one':
 >>>> (.text+0x147f): undefined reference to `gpiod_export'

Sorry about that. I have sent you the fix in a separate mail. Please 
meld it into the culprit commit to fix this.

Thanks,
Alex.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/