mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-29 19:21:31 -04:00
drivers: misc: ti-st: Use int instead of fuzzy char for callback status
On mips and parisc:
drivers/bluetooth/btwilink.c: In function 'ti_st_open':
drivers/bluetooth/btwilink.c:174:21: warning: overflow in implicit constant conversion [-Woverflow]
hst->reg_status = -EINPROGRESS;
drivers/nfc/nfcwilink.c: In function 'nfcwilink_open':
drivers/nfc/nfcwilink.c:396:31: warning: overflow in implicit constant conversion [-Woverflow]
drv->st_register_cb_status = -EINPROGRESS;
There are actually two issues:
1. Whether "char" is signed or unsigned depends on the architecture.
As the completion callback data is used to pass a (negative) error
code, it should always be signed.
2. EINPROGRESS is 150 on mips, 245 on parisc.
Hence -EINPROGRESS doesn't fit in a signed 8-bit number.
Change the callback status from "char" to "int" to fix these.
Signed-off-by: Geert Uytterhoeven <[email protected]>
Acked-by: Mauro Carvalho Chehab <[email protected]>
Acked-by: Samuel Ortiz <[email protected]>
Signed-off-by: Marcel Holtmann <[email protected]>
This commit is contained in:
parent
858d68f102
commit
4360fa22ad
5 changed files with 7 additions and 7 deletions
|
|
@ -94,7 +94,7 @@ struct nfcwilink {
|
|||
struct nci_dev *ndev;
|
||||
unsigned long flags;
|
||||
|
||||
char st_register_cb_status;
|
||||
int st_register_cb_status;
|
||||
long (*st_write) (struct sk_buff *);
|
||||
|
||||
struct completion completed;
|
||||
|
|
@ -320,7 +320,7 @@ exit:
|
|||
}
|
||||
|
||||
/* Called by ST when registration is complete */
|
||||
static void nfcwilink_register_complete(void *priv_data, char data)
|
||||
static void nfcwilink_register_complete(void *priv_data, int data)
|
||||
{
|
||||
struct nfcwilink *drv = priv_data;
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue