From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUILD BREAKAGE] versatile, LEDS updates
Date: Fri, 29 Jun 2012 11:33:13 +0100 [thread overview]
Message-ID: <20120629103313.GA16319@n2100.arm.linux.org.uk> (raw)
I've just added Versatile to the build system, and the result is not
encouraging. The integration of the LEDS code into Versatile breaks
its build:
http://www.arm.linux.org.uk/developer/build/result.php?type=build&idx=1281
arch/arm/plat-versatile/leds.c: In function 'versatile_leds_init':
arch/arm/plat-versatile/leds.c:91: error: 'struct led_classdev' has no member named 'trigger_data'
This needs fixing before the LEDS code goes into mainline.
How well tested is the LEDS code? Was it only tested with a set of
specifically updated configurations (it looks that way to me.) Was
it ever tested with randconfig?
next reply other threads:[~2012-06-29 10:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 10:33 Russell King - ARM Linux [this message]
2012-06-29 11:45 ` [BUILD BREAKAGE] versatile, LEDS updates Russell King - ARM Linux
2012-07-02 8:39 ` Russell King - ARM Linux
2012-07-02 15:40 ` Arnd Bergmann
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=20120629103313.GA16319@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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 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).