Prev: [2.6.34-rc5-git6] EIP: is at inet6_csk_bind_conflict + 06xe/0xb7 [ipv6]
Next: [PATCH 05/11] staging: crystalhd: clean up crystalhd_setup_cmd_context() return code
From: Yoichi Yuasa on 25 Apr 2010 09:50 Signed-off-by: Yoichi Yuasa <yuasa(a)linux-mips.org> --- drivers/staging/crystalhd/bc_dts_defs.h | 13 ------------- drivers/staging/crystalhd/crystalhd_lnx.c | 2 -- 2 files changed, 0 insertions(+), 15 deletions(-) diff --git a/drivers/staging/crystalhd/bc_dts_defs.h b/drivers/staging/crystalhd/bc_dts_defs.h index e825312..d7e6a9e 100644 --- a/drivers/staging/crystalhd/bc_dts_defs.h +++ b/drivers/staging/crystalhd/bc_dts_defs.h @@ -34,28 +34,15 @@ typedef enum _BC_STATUS { BC_STS_INV_ARG = 1, BC_STS_BUSY = 2, BC_STS_NOT_IMPL = 3, - BC_STS_PGM_QUIT = 4, - BC_STS_NO_ACCESS = 5, BC_STS_INSUFF_RES = 6, BC_STS_IO_ERROR = 7, BC_STS_NO_DATA = 8, - BC_STS_VER_MISMATCH = 9, BC_STS_TIMEOUT = 10, BC_STS_FW_CMD_ERR = 11, - BC_STS_DEC_NOT_OPEN = 12, BC_STS_ERR_USAGE = 13, BC_STS_IO_USER_ABORT = 14, - BC_STS_IO_XFR_ERROR = 15, - BC_STS_DEC_NOT_STARTED = 16, - BC_STS_FWHEX_NOT_FOUND = 17, - BC_STS_FMT_CHANGE = 18, - BC_STS_HIF_ACCESS = 19, BC_STS_CMD_CANCELLED = 20, BC_STS_FW_AUTH_FAILED = 21, - BC_STS_BOOTLOADER_FAILED = 22, - BC_STS_CERT_VERIFY_ERROR = 23, - BC_STS_DEC_EXIST_OPEN = 24, - BC_STS_PENDING = 25, BC_STS_CLK_NOCHG = 26, /* Must be the last one.*/ diff --git a/drivers/staging/crystalhd/crystalhd_lnx.c b/drivers/staging/crystalhd/crystalhd_lnx.c index 3eac70a..6ef54e3 100644 --- a/drivers/staging/crystalhd/crystalhd_lnx.c +++ b/drivers/staging/crystalhd/crystalhd_lnx.c @@ -245,8 +245,6 @@ static int chd_dec_api_cmd(struct crystalhd_adp *adp, unsigned long ua, rc = chd_dec_proc_user_data(adp, temp, ua, 0); if (!rc) { sts = func(&adp->cmds, temp); - if (sts == BC_STS_PENDING) - sts = BC_STS_NOT_IMPL; temp->udata.RetSts = sts; rc = chd_dec_proc_user_data(adp, temp, ua, 1); } -- 1.7.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |