From 570daf2321afbdc0b48b3c7c0fabd10a579b4360 Mon Sep 17 00:00:00 2001 From: Benjamin Berg Date: Tue, 2 Jun 2020 16:33:26 +0200 Subject: [PATCH] upeksonly: Remove ABORT_SSM constant This was not used. The old driver used this if creating a USB transfer failed, however, we delay any such failures (which cannot really happen) into the callback today, where the error is handled differently. --- libfprint/drivers/upeksonly.c | 8 -------- 1 file changed, 8 deletions(-) diff --git a/libfprint/drivers/upeksonly.c b/libfprint/drivers/upeksonly.c index 960edaab..67cd6d79 100644 --- a/libfprint/drivers/upeksonly.c +++ b/libfprint/drivers/upeksonly.c @@ -47,9 +47,6 @@ enum { enum sonly_kill_transfers_action { NOT_KILLING = 0, - /* abort a SSM with an error code */ - ABORT_SSM, - /* report an image session error */ IMG_SESSION_ERROR, @@ -176,11 +173,6 @@ last_transfer_killed (FpImageDevice *dev) switch (self->killing_transfers) { - case ABORT_SSM: - fp_dbg ("abort ssm error %s", self->kill_error->message); - fpi_ssm_mark_failed (self->kill_ssm, g_steal_pointer (&self->kill_error)); - return; - case ITERATE_SSM: fp_dbg ("iterate ssm"); fpi_ssm_next_state (self->kill_ssm);