linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bryan Wu <bryan.wu@canonical.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Fabio Baltieri <fabio.baltieri@gmail.com>
Subject: Re: linux-next: build failure after merge of the leds tree
Date: Wed, 13 Jun 2012 12:25:05 +0800	[thread overview]
Message-ID: <CAK5ve-JZ6zH=GZ2CHovNty56LbtXSWhPCU6Nanfh9rHBnws6Cw@mail.gmail.com> (raw)
In-Reply-To: <20120613141041.199421c4b922655cbcfbe14d@canb.auug.org.au>

On Wed, Jun 13, 2012 at 12:10 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Bryan,
>
> After merging the leds tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/leds/led-core.c: In function 'led_set_software_blink':
> drivers/leds/led-core.c:44:2: error: implicit declaration of function 'led_stop_software_blink' [-Werror=implicit-function-declaration]
>
> Caused by commit eb91300a9786 ("leds: fix led_brightness_set when
> soft-blinking").
>
> This is exactly the problem I reported on June 8 and was fixed in
> next-20120612 ...
>
> I have used the leds tree from next-20120612 for today.

Thanks for raising this. I rebuilt the for-next branch.

-Bryan

  reply	other threads:[~2012-06-13  4:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-13  4:10 linux-next: build failure after merge of the leds tree Stephen Rothwell
2012-06-13  4:25 ` Bryan Wu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-09-26 20:53 broonie
2022-09-26 21:18 ` Pavel Machek
2022-09-23  4:31 Stephen Rothwell
2020-01-06  3:21 Stephen Rothwell
2020-01-06  9:31 ` Guido Günther
2020-01-06 10:32   ` Pavel Machek
2020-01-06 15:52     ` Guido Günther
2019-07-25  2:31 Stephen Rothwell
2019-07-25 18:44 ` Jacek Anaszewski
2013-06-17  5:29 Stephen Rothwell
2013-06-17  6:26 ` Alexander Shiyan
2013-06-21  0:16   ` Stephen Rothwell
2013-06-21  0:27     ` Grant Likely
2013-01-23  4:12 Stephen Rothwell
2013-01-23  6:05 ` Kim, Milo
2012-06-08  2:44 Stephen Rothwell
2012-06-08  3:33 ` Bryan Wu

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='CAK5ve-JZ6zH=GZ2CHovNty56LbtXSWhPCU6Nanfh9rHBnws6Cw@mail.gmail.com' \
    --to=bryan.wu@canonical.com \
    --cc=fabio.baltieri@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).