Linux-Next discussions
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Brett Rudley <brudley@broadcom.com>,
	Arend van Spriel <arend@broadcom.com>
Subject: Re: linux-next: Tree for May 15 (wireless/brcm)
Date: Wed, 15 May 2013 10:42:19 -0700	[thread overview]
Message-ID: <5193C8FB.3070408@infradead.org> (raw)
In-Reply-To: <20130515132627.817585a3d9fb3a3e502eb586@canb.auug.org.au>

On 05/14/13 20:26, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20130514:
> 

on x86_64:

drivers/built-in.o: In function `brcms_led_unregister':
(.text+0x136f0e): undefined reference to `led_classdev_unregister'
drivers/built-in.o: In function `brcms_led_register':
(.text+0x1370b5): undefined reference to `led_classdev_register'

when CONFIG_NEW_LEDS is not enabled.


-- 
~Randy

  reply	other threads:[~2013-05-15 17:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15  3:26 linux-next: Tree for May 15 Stephen Rothwell
2013-05-15 17:42 ` Randy Dunlap [this message]
2013-05-15 17:59 ` linux-next: Tree for May 15 (crypto /crct10dif) Randy Dunlap
2013-05-16  3:57   ` Xiong Zhou
2013-05-16  7:22     ` Geert Uytterhoeven
2013-05-16 16:09       ` Tim Chen
2013-05-16 16:59       ` Tim Chen
2013-05-16 18:03         ` Tim Chen
2013-05-17  3:09           ` Xiong Zhou
2013-05-20 11:47           ` Herbert Xu
2013-05-20 12:14             ` Herbert Xu
2013-05-20 19:09             ` Tim Chen
2013-05-21 13:46               ` Herbert Xu
2013-05-17  3:06       ` Xiong Zhou
2013-05-15 21:03 ` [PATCH -next] platform/x86: fix amilo-rfkill build errors Randy Dunlap

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=5193C8FB.3070408@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=arend@broadcom.com \
    --cc=brudley@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --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