linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	NeilBrown <neilb@suse.de>, Richard Purdie <rpurdie@rpsys.net>
Subject: Re: linux-next: Tree for Dec 16 (leds/tca6507)
Date: Fri, 16 Dec 2011 14:25:25 -0800	[thread overview]
Message-ID: <4EEBC555.4010600@xenotime.net> (raw)
In-Reply-To: <20111216170042.650147ec79e792dce950f6e3@canb.auug.org.au>

On 12/15/2011 10:00 PM, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20111215:


When GPIOLIB is not enabled:

drivers/leds/leds-tca6507.c:158:20: error: field 'gpio' has incomplete type
drivers/leds/leds-tca6507.c: In function 'tca6507_gpio_set_value':
drivers/leds/leds-tca6507.c:534:29: warning: type defaults to 'int' in declaration of '__mptr'
drivers/leds/leds-tca6507.c:534:29: warning: initialization from incompatible pointer type
drivers/leds/leds-tca6507.c: In function 'tca6507_probe':
drivers/leds/leds-tca6507.c:618:3: error: implicit declaration of function 'gpiochip_add'
drivers/leds/leds-tca6507.c: In function 'tca6507_remove':
drivers/leds/leds-tca6507.c:651:3: error: implicit declaration of function 'gpiochip_remove'


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

      parent reply	other threads:[~2011-12-16 21:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16  6:00 linux-next: Tree for Dec 16 Stephen Rothwell
2011-12-16 19:15 ` linux-next: Tree for Dec 16 (usb/gadget/langwell) Randy Dunlap
2011-12-16 22:35   ` Felipe Balbi
2011-12-19 13:26     ` Felipe Balbi
2011-12-16 19:42 ` linux-next: Tree for Dec 16 (intel_scu & abp_timer) Randy Dunlap
2011-12-16 18:50   ` Alan Cox
2011-12-16 22:25 ` Randy Dunlap [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=4EEBC555.4010600@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=rpurdie@rpsys.net \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).