mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: akpm@linux-foundation.org,
	Esben Haabendal <eha@doredevelopment.dk>,
	Richard Purdie <rpurdie@rpsys.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mmotm 2011-05-06-16-39 uploaded (leds)
Date: Fri, 6 May 2011 18:23:41 -0700	[thread overview]
Message-ID: <20110506182341.d2cd8a19.rdunlap@xenotime.net> (raw)
In-Reply-To: <201105070015.p470FlAR013200@imap1.linux-foundation.org>

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'

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2011-05-07  1: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 ` Randy Dunlap [this message]
2011-05-07  6:23   ` mmotm 2011-05-06-16-39 uploaded (leds) Esben Haabendal
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=20110506182341.d2cd8a19.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=akpm@linux-foundation.org \
    --cc=eha@doredevelopment.dk \
    --cc=linux-kernel@vger.kernel.org \
    --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