user/sven/linux.git/drivers/ipack, branch v4.14.219

ipack: Improve a size determination in ipack_bus_register()

2017-05-18T14:59:06Z

Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. Signed-off-by: Markus Elfring Acked-by: Samuel Iglesias Gonsálvez Signed-off-by: Greg Kroah-Hartman

ipack: Delete an error message for a failed memory allocation in ipack_device_read_id()

2017-05-18T14:59:06Z

Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Link: http://events.linuxfoundation.org/sites/events/files/slides/LCJ16-Refactor_Strings-WSang_0.pdf Signed-off-by: Markus Elfring Acked-by: Samuel Iglesias Gonsálvez Signed-off-by: Greg Kroah-Hartman

ipack: print a hex number after a 0x prefix

2016-10-28T01:43:43Z

It makes the result hard to interpret correctly if a base 10 number is prefixed by 0x. So change to a hex number. Link: http://lkml.kernel.org/r/20161026125658.25728-4-u.kleine-koenig@pengutronix.de Signed-off-by: Uwe Kleine-König Cc: Samuel Iglesias Gonsalvez Cc: Jens Taprogge Cc: Greg Kroah-Hartman Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

tty: Replace ASYNC_INITIALIZED bit and update atomically

2016-04-30T16:26:55Z

Replace ASYNC_INITIALIZED bit in the tty_port::flags field with TTY_PORT_INITIALIZED bit in the tty_port::iflags field. Introduce helpers tty_port_set_initialized() and tty_port_initialized() to abstract atomic bit ops. Note: the transforms for test_and_set_bit() and test_and_clear_bit() are unnecessary as the state transitions are already mutually exclusive; the tty lock prevents concurrent open/close/hangup. Signed-off-by: Peter Hurley Signed-off-by: Greg Kroah-Hartman

ipoctal: clear break interrupt as soon as it occurs

2014-09-24T06:26:42Z

In some condition we receive the break interrupt but nothing is putted in the Rx FIFO and the correspondend bit in the status register is not set. Thus, no-one clear the interrupt and the handler will be called forever. This patch clear the break interrupt as soon as it occurs. Then, if the break character '\0' is putted in the fifo we will manage it. We can also unmask the Break interrupt but its bit in ISR is still set on break. So I think is better to keep the registers clean. Signed-off-by: Federico Vaga Acked-by: Samuel Iglesias Gonsalvez Signed-off-by: Greg Kroah-Hartman

ipoctal: get carrier driver to avoid rmmod

2014-09-24T06:13:13Z

Signed-off-by: Federico Vaga Acked-by: Samuel Iglesias Gonsalvez Signed-off-by: Greg Kroah-Hartman

ipack: save carrier owner to allow device to get it

2014-09-24T06:13:13Z

There was not any kind of protection against carrier driver removal. In this way, device driver can 'get' the carrier driver when it is using it. Signed-off-by: Federico Vaga Acked-by: Samuel Iglesias Gonsalvez Signed-off-by: Greg Kroah-Hartman

ipoctal: reset function istead of duplicate code

2014-09-24T06:13:13Z

Signed-off-by: Federico Vaga Acked-by: Samuel Iglesias Gonsalvez Signed-off-by: Greg Kroah-Hartman

drivers/ipack/devices/ipoctal.h: Fix typo in include guard

2014-09-24T06:13:13Z

Signed-off-by: Rasmus Villemoes Acked-by: Samuel Iglesias Gonsalvez Signed-off-by: Greg Kroah-Hartman

ipack: Replace DEFINE_PCI_DEVICE_TABLE macro use

2014-07-18T23:50:55Z

We should prefer `struct pci_device_id` over `DEFINE_PCI_DEVICE_TABLE` to meet kernel coding style guidelines. This issue was reported by checkpatch. Signed-off-by: Benoit Taine Acked-by: Samuel Iglesias Gonsalvez Signed-off-by: Greg Kroah-Hartman