[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <5073FA9D.8080501@evidence.eu.com>
Date: Tue, 09 Oct 2012 12:21:17 +0200
From: Claudio Scordino <claudio@...dence.eu.com>
To: linux-usb@...r.kernel.org
CC: Linux Kernel <linux-kernel@...r.kernel.org>,
Greg KH <gregkh@...uxfoundation.org>
Subject: [PATCH RESEND] umc-bus.c: fix usage of device_trylock
Hi all.
I've not received any feedback about this patch, so I'm resending just
to check if someone is going to take care of it.
The patch fixes the usage of device_trylock inside the driver umc-bus.c:
device_trylock has the same semantics of mutex_trylock, so it returns 1
if the lock has been acquired successfully.
Best regards,
Claudio
Subject: umc-bus.c: fix usage of device_trylock
From: Claudio Scordino <claudio@...dence.eu.com>
Fix usage of device_trylock. It has the same semantics of mutex_trylock, so it
returns 1 if the lock has been acquired successfully.
Signed-off-by: Claudio Scordino <claudio@...dence.eu.com>
Signed-off-by: Bruno Morelli <bruno@...dence.eu.com>
---
drivers/uwb/umc-bus.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/uwb/umc-bus.c b/drivers/uwb/umc-bus.c
index 82a84d5..5c5b3fc 100644
--- a/drivers/uwb/umc-bus.c
+++ b/drivers/uwb/umc-bus.c
@@ -63,7 +63,7 @@ int umc_controller_reset(struct umc_dev *umc)
struct device *parent = umc->dev.parent;
int ret = 0;
- if (device_trylock(parent))
+ if (!device_trylock(parent))
return -EAGAIN;
ret = device_for_each_child(parent, parent, umc_bus_pre_reset_helper);
if (ret >= 0)
--
1.7.1
--
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