From: "Pali Rohár" <pali.rohar@gmail.com>
To: Bryan Wu <cooloney@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>,
"rpurdie@rpsys.net" <rpurdie@rpsys.net>,
Linux LED Subsystem <linux-leds@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>, milo kim <milo.kim@ti.com>,
Sebastian Reichel <sre@debian.org>,
Sebastian Reichel <sre@ring0.de>
Subject: Re: Broken locking in leds-lp5523.c
Date: Thu, 9 Jan 2014 15:24:53 +0100 [thread overview]
Message-ID: <201401091524.53417@pali> (raw)
In-Reply-To: <CAK5ve-Kk9BuH=56F98aZOgPS+w-=8iF0HtpOYWNjRN8am2Zqjg@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1004 bytes --]
On Wednesday 08 January 2014 01:32:15 Bryan Wu wrote:
> On Tue, Jan 7, 2014 at 12:42 PM, Pavel Machek <pavel@ucw.cz>
wrote:
> > Hi!
> >
> > There's some locking weirdness, and few missing comments in
> > lp5523 driver.
> >
> > Now, this is untested patch from my reverse-engineering. I
> > hope I understood things right...
> >
> > In particular, there's unbalanced unlock in
> > lp5523_update_program_memory, and
> > lp5523_update_program_memory needs to be protected by the
> > lock.
> >
> > Comments? Does someone maintain this?
>
> Actually the locking issue was fixed in my for-next branch,
> http://git.kernel.org/cgit/linux/kernel/git/cooloney/linux-led
> s.git/commit/?h=for-next&id=0d70bdb957cde2c25a4b3e4c93d0d33403
> 795be9
>
> Thanks,
> -Bryan
>
Now, with linus tree lp5523 driver does not work without above
commit on Nokia N900 device. I think that commit should go to
3.13 and stable... What do you think?
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-01-09 14:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 20:42 Broken locking in leds-lp5523.c Pavel Machek
2014-01-07 20:42 ` Pavel Machek
2014-01-07 23:57 ` Bryan Wu
2014-01-09 23:08 ` Pavel Machek
2014-01-08 0:32 ` Bryan Wu
2014-01-09 14:24 ` Pali Rohár [this message]
2014-01-09 17:51 ` Bryan Wu
2014-01-09 22:45 ` Pavel Machek
2014-01-09 23:13 ` [trivial] Comment improvements for lp5523 and friend Pavel Machek
2014-02-06 19:36 ` Bryan Wu
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=201401091524.53417@pali \
--to=pali.rohar@gmail.com \
--cc=cooloney@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=milo.kim@ti.com \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.net \
--cc=sre@debian.org \
--cc=sre@ring0.de \
/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.