public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>,
	Philippe R?tornaz <philippe.retornaz@epfl.ch>,
	linux-arm-kernel@lists.infradead.org,
	maramaopercheseimorto@gmail.com, sameo@linux.intel.com,
	s.hauer@pengutronix.de, linux-kernel@vger.kernel.org,
	valentin.longchamp@epfl.ch
Subject: Re: [PATCH 1/2] mc13783: add LED support
Date: Wed, 26 May 2010 08:58:32 -0700	[thread overview]
Message-ID: <20100526155831.GA18834@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1274875268.24079.1.camel@rex>

On Wed, May 26, 2010 at 01:01:08PM +0100, Richard Purdie wrote:
> On Mon, 2010-05-17 at 21:00 +0100, Mark Brown wrote:

> > It'd be nice to add helpers for this to the LED core, there's quite a
> > few drivers implementing this idiom now - a flag that does the deferring
> > of the set() for example.

> Agreed, or a wrapper around the core which deferred implementations
> could just use. I'm open to patches :)

In my copious free time, perhaps.  I was kind of hoping someone actively
working on a driver could be inspired to do the work :)

  reply	other threads:[~2010-05-26 15:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-17 16:40 [PATCH 0/2] mc13783: LED support Philippe Rétornaz
2010-05-17 16:40 ` [PATCH 1/2] mc13783: add " Philippe Rétornaz
2010-05-17 16:40   ` [PATCH 2/2] mx31moboard: Add MC13783 led support Philippe Rétornaz
2010-05-17 19:02   ` [PATCH 1/2] mc13783: add LED support Uwe Kleine-König
2010-05-17 20:00     ` Mark Brown
2010-05-26 12:01       ` Richard Purdie
2010-05-26 15:58         ` Mark Brown [this message]
2010-05-18 11:27     ` Philippe Rétornaz
2010-05-25 14:57       ` Daniel Mack
2010-05-25 15:06         ` Philippe Rétornaz
2010-05-26 12:03           ` Richard Purdie

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=20100526155831.GA18834@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maramaopercheseimorto@gmail.com \
    --cc=philippe.retornaz@epfl.ch \
    --cc=rpurdie@rpsys.net \
    --cc=s.hauer@pengutronix.de \
    --cc=sameo@linux.intel.com \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=valentin.longchamp@epfl.ch \
    /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