Attachment 69582 Details for Bug 56439 – 0001-AES1610-driver-cleanup-part-1.patch

[patch] 0001-AES1610-driver-cleanup-part-1.patch

0001-AES1610-driver-cleanup-part-1.patch (text/plain), 1.35 KB, created by Vasily Khoruzhick on 2012-11-05 19:48:23 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Vasily Khoruzhick

Created: 2012-11-05 19:48:23 UTC

Size: 1.35 KB

patch

obsolete

>From dd5f3a46439b0959f298a70fd47d33265dd5b5fd Mon Sep 17 00:00:00 2001
>From: Vasily Khoruzhick <anarsoul@gmail.com>
>Date: Sat, 20 Oct 2012 12:26:38 +0300
>Subject: [PATCH 1/2] AES1610: driver cleanup, part #1
>
>Fix warnings reported by gcc
>---
> libfprint/drivers/aes1610.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
>diff --git a/libfprint/drivers/aes1610.c b/libfprint/drivers/aes1610.c
>index 8b81a80..fe046e3 100644
>--- a/libfprint/drivers/aes1610.c
>+++ b/libfprint/drivers/aes1610.c
>@@ -500,7 +500,6 @@ static void finger_det_reqs_cb(struct fp_img_dev *dev, int result, void *user_da
> static void start_finger_detection(struct fp_img_dev *dev)
> {
> 	struct aes1610_dev *aesdev = dev->priv;
>-	struct libusb_transfer *transfer;
> 
> 	if (aesdev->deactivating) {
> 		complete_deactivation(dev);
>@@ -780,7 +779,7 @@ static int adjust_gain(unsigned char *buffer, int status)
> 
> /*
>  * Restore the default gain values */
>-static void restore_gain()
>+static void restore_gain(void)
> {
> 	strip_scan_reqs[0].value = list_BE_values[0];
> 	strip_scan_reqs[1].value = 0x04;
>@@ -815,7 +814,6 @@ static void capture_read_strip_cb(struct libusb_transfer *transfer)
> 	struct aes1610_dev *aesdev = dev->priv;
> 	unsigned char *data = transfer->buffer;
> 	int sum, i;
>-	int threshold;
> 
> 	if (transfer->status != LIBUSB_TRANSFER_COMPLETED) {
> 		fpi_ssm_mark_aborted(ssm, -EIO);
>-- 
>1.8.0
>

Actions: View | Splinter Review

Attachments on bug 56439: 69126 | 69127 | 69128 | 69129 | 69130 | 69131 | 69582 | 69583

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.