Files
linux/drivers
Geert Uytterhoeven 4360fa22ad 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 <geert@linux-m68k.org>
Acked-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Acked-by: Samuel Ortiz <sameo@linux.intel.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
2016-07-17 19:59:26 +02:00
..
2016-07-01 05:58:26 -04:00
2016-05-31 22:17:05 +05:30
2016-06-09 22:38:16 +02:00
2016-06-23 00:29:32 +02:00
2016-06-09 14:28:28 -06:00
2016-05-27 15:26:11 -07:00
2016-04-30 13:56:46 -07:00
2016-06-15 09:51:35 +01:00
2016-05-29 22:32:27 -07:00
2016-05-20 18:33:37 -07:00
2016-06-07 15:56:31 -07:00
2016-04-30 14:15:56 -07:00
2016-05-01 14:11:12 -07:00
2016-05-31 21:25:52 -06:00
2016-07-01 05:32:17 -04:00
2016-05-31 08:20:43 +03:00