Stefani Seibold 498d319bb5 kfifo API type safety ...

This patch enhances the type safety for the kfifo API.  It is now safe
to put const data into a non const FIFO and the API will now generate a
compiler warning when reading from the fifo where the destination
address is pointing to a const variable.

As a side effect the kfifo_put() does now expect the value of an element
instead a pointer to the element.  This was suggested Russell King.  It
make the handling of the kfifo_put easier since there is no need to
create a helper variable for getting the address of a pointer or to pass
integers of different sizes.

IMHO the API break is okay, since there are currently only six users of
kfifo_put().

The code is also cleaner by kicking out the "if (0)" expressions.

[[email protected]: coding-style fixes]
Signed-off-by: Stefani Seibold <[email protected]>
Cc: Russell King <[email protected]>
Cc: Hauke Mehrtens <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>

2013-11-15 09:32:23 +09:00

..

bytestream-example.c

kfifo API type safety

2013-11-15 09:32:23 +09:00

dma-example.c

kfifo API type safety

2013-11-15 09:32:23 +09:00

inttype-example.c

kfifo API type safety

2013-11-15 09:32:23 +09:00

Makefile

…

record-example.c

…