All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Richard Purdie <rpurdie@linux.intel.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] leds: Fix locking for WM8350
Date: Sat, 15 Nov 2008 19:14:14 +0000	[thread overview]
Message-ID: <20081115191414.GA12907@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20081115185119.GA19900@elf.ucw.cz>

On Sat, Nov 15, 2008 at 07:51:20PM +0100, Pavel Machek wrote:
> On Sat 2008-11-15 17:50:50, Mark Brown wrote:

> > Yes, that'd be safer though I'd be surprised to see systems that could
> > trigger it.

> Yes, they are uncommon. They exist; SPARC, IIRC. Plus you need

Exceptionally uncommon with the systems the WM8350 gets used with -
it's a primary PMIC for mobile devices so anything other than
uniprocessor ARM would be surprising.

> barriers on anything SMP... Just use atomic_t.

I was intending to do so next time I spin the patch.  Andrew had some
other comments and I don't have any test systems when I'm not in the
office anyway.

  reply	other threads:[~2008-11-15 19:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-13 12:39 [PATCH] leds: Add WM8350 LED driver Mark Brown
2008-11-13 14:57 ` [PATCH] leds: Fix locking for WM8350 Mark Brown
2008-11-15 17:31   ` Pavel Machek
2008-11-15 17:50     ` Mark Brown
2008-11-15 18:51       ` Pavel Machek
2008-11-15 19:14         ` Mark Brown [this message]
2008-11-17 15:33           ` Richard Purdie
2008-11-17 23:05             ` Mark Brown
2008-11-18  8:33             ` Pavel Machek
2008-11-14 23:19 ` [PATCH] leds: Add WM8350 LED driver Andrew Morton
2008-11-17 11:57   ` Mark Brown
2008-11-15 17:29 ` Pavel Machek
2008-11-15 17:43   ` Mark Brown

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=20081115191414.GA12907@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=rpurdie@linux.intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.