[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdapB5x2MEKKvDU2MBKPVKXwYCx+HDYFUcY0vskeVOxPTg@mail.gmail.com>
Date: Thu, 18 Oct 2012 20:35:29 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Bryan Wu <cooloney@...il.com>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
Miles Lane <miles.lane@...il.com>,
akpm <akpm@...ux-foundation.org>,
Linux LED Subsystem <linux-leds@...r.kernel.org>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ledtrig-cpu: use spin_lock to replace mutex lock
On Thu, Oct 18, 2012 at 8:18 PM, Bryan Wu <cooloney@...il.com> wrote:
> Mutex lock is not safe in atomic context like the bug reported by
> Miles Lane:
(...)
> This patch replace mutex lock with spin lock which is safe for this case.
>
> Reported-by: Miles Lane <miles.lane@...il.com>
> Reported-by: Rafael J. Wysocki <rjw@...k.pl>
> Cc: Linus Walleij <linus.walleij@...aro.org>
> Signed-off-by: Bryan Wu <cooloney@...il.com>
Looks correct to me:
Acked-by: Linus Walleij <linus.walleij@...aro.org>
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists