From: Esben Haabendal <eha@doredevelopment.dk>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: akpm@linux-foundation.org, Richard Purdie <rpurdie@rpsys.net>,
linux-kernel@vger.kernel.org
Subject: Re: mmotm 2011-05-06-16-39 uploaded (leds)
Date: Sat, 07 May 2011 08:23:53 +0200 [thread overview]
Message-ID: <1304749433.3530.3.camel@eha.ulstruplund.dk> (raw)
In-Reply-To: <20110506182341.d2cd8a19.rdunlap@xenotime.net>
On Fri, 2011-05-06 at 18:23 -0700, Randy Dunlap wrote:
> On Fri, 06 May 2011 16:39:31 -0700 akpm@linux-foundation.org wrote:
>
> > The mm-of-the-moment snapshot 2011-05-06-16-39 has been uploaded to
> >
> > http://userweb.kernel.org/~akpm/mmotm/
> >
> > and will soon be available at
> >
> > git://zen-kernel.org/kernel/mmotm.git
> >
> > It contains the following patches against 2.6.39-rc6:
>
>
> As reported on April 15 of 2011 in
> Subject: Re: mmotm 2011-04-14-15-08 uploaded (leds)
>
>
> from leds-support-automatic-start-of-blinking-with-ledtrig-timer.patch:
>
> This build error happened several times when
> CONFIG_LEDS_TRIGGERS is not enabled:
>
> drivers/leds/led-class.c:134: error: 'struct led_classdev' has no member named 'trigger_data'
Hmm... This is in led_set_software_blink() which is only used if
CONFIG_LEDS_TRIGGERS is enabled. It might make sense to leave out all
the blink related functions when CONFIG_LEDS_TRIGGERS is not enabled.
I am just leaving for some weekend activities, but I will happy to write
a patch for it sunday or perhaps monday.
/Esben
next prev parent reply other threads:[~2011-05-07 6:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 23:39 mmotm 2011-05-06-16-39 uploaded akpm
2011-05-07 1:23 ` mmotm 2011-05-06-16-39 uploaded (leds) Randy Dunlap
2011-05-07 6:23 ` Esben Haabendal [this message]
2011-05-09 9:16 ` [PATCH] leds: fix build with CONFIG_LEDS_TRIGGERS disabled Esben Haabendal
2011-05-09 15:51 ` Randy Dunlap
2011-05-07 1:35 ` mmotm 2011-05-06-16-39 uploaded (fs/proc/task_mmu) Randy Dunlap
2011-05-07 5:37 ` Stephen Wilson
2011-05-10 8:57 ` mmotm 2011-05-06-16-39 uploaded KAMEZAWA Hiroyuki
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=1304749433.3530.3.camel@eha.ulstruplund.dk \
--to=eha@doredevelopment.dk \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=rpurdie@rpsys.net \
/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
Powered by JetHome