[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1daac2ee8782465386c2659e943d11e4@US-EXCH13-2.na.uis.unisys.com>
Date: Mon, 20 Jun 2016 12:18:12 +0000
From: "Sell, Timothy C" <Timothy.Sell@...sys.com>
To: Binoy Jayan <binoy.jayan@...aro.org>,
"Kershner, David A" <David.Kershner@...sys.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC: Arnd Bergmann <arnd@...db.de>,
*S-Par-Maintainer <SParMaintainer@...sys.com>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] staging: unisys: visorbus: Replace semaphore with mutex
> -----Original Message-----
> From: Binoy Jayan [mailto:binoy.jayan@...aro.org]
> Sent: Monday, June 20, 2016 1:07 AM
> To: Kershner, David A; Greg Kroah-Hartman
> Cc: Arnd Bergmann; *S-Par-Maintainer; devel@...verdev.osuosl.org; linux-
> kernel@...r.kernel.org; Binoy Jayan
> Subject: [PATCH] staging: unisys: visorbus: Replace semaphore with mutex
>
> The semaphore 'visordriver_callback_lock' is a simple mutex, so
> it should be written as one. Semaphores are going away in the future.
>
Thanks Binoy, but we already submitted a patch for this issue on June 11,
and are currently awaiting its acceptance into staging. See:
* [PATCH RESEND 12/28] staging: unisys: visorbus: Make visordriver_callback_lock a mutex
(http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2016-June/090861.html)
* [PATCH RESEND 00/28] staging: unisys: fix visorbus & visorinput issues raised by tglx
(http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2016-June/090854.html)
Tim Sell
Powered by blists - more mailing lists