From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Bryan Wu <bryan.wu@canonical•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Fabio Baltieri <fabio.baltieri@gmail•com>
Subject: linux-next: build failure after merge of the leds tree
Date: Fri, 8 Jun 2012 12:44:48 +1000 [thread overview]
Message-ID: <20120608124448.2ff862098d474dc6a567dc46@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 596 bytes --]
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 12b204f41034 ("leds: fix led_brightness_set when
soft-blinking"). Please build test this stuff.
I have used the leds tree from next-20120607 for today.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2012-06-08 2:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 2:44 Stephen Rothwell [this message]
2012-06-08 3:33 ` linux-next: build failure after merge of the leds tree Bryan Wu
-- strict thread matches above, loose matches on Subject: below --
2012-06-13 4:10 Stephen Rothwell
2012-06-13 4:25 ` Bryan Wu
2013-01-23 4:12 Stephen Rothwell
2013-01-23 6:05 ` Kim, Milo
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
2019-07-25 2:31 Stephen Rothwell
2019-07-25 18:44 ` Jacek Anaszewski
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
2022-09-23 4:31 Stephen Rothwell
2022-09-26 20:53 broonie
2022-09-26 21:18 ` Pavel Machek
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=20120608124448.2ff862098d474dc6a567dc46@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=bryan.wu@canonical$(echo .)com \
--cc=fabio.baltieri@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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