All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Courbot <acourbot@nvidia.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	<gnurou@gmail.com>
Subject: Re: [grant:gpio/next 10/16] gpiolib.c:undefined reference to `gpiod_unexport'
Date: Sun, 10 Feb 2013 23:04:52 +0900	[thread overview]
Message-ID: <5117A904.4040309@nvidia.com> (raw)
In-Reply-To: <CACxGe6tAEX7o9dxNTXtwKwzZHmEteKAS+7uy4j-DTX_2V583tg@mail.gmail.com>

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@intel.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.

      parent reply	other threads:[~2013-02-10 14:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51166e1c.NRfQN8VgI14zuNwf%fengguang.wu@intel.com>
2013-02-09 16:34 ` [grant:gpio/next 10/16] gpiolib.c:undefined reference to `gpiod_unexport' Grant Likely
2013-02-10 14:00   ` [PATCH] gpiolib: fix link error when sysfs is not built Alexandre Courbot
2013-02-10 18:43     ` Grant Likely
2013-02-10 14:04   ` Alex Courbot [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=5117A904.4040309@nvidia.com \
    --to=acourbot@nvidia.com \
    --cc=gnurou@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --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 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.