A-Team_Digital_Solutions/android_kernel_motorola_sm6375
Watch
2
0
Fork
You've already forked android_kernel_motorola_sm6375
 0
mirror of https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git synced 2026-10-28 02:32:09 -04:00
Code Issues Projects Releases Packages Wiki Activity

connector: make callback argument type explicit

Browse source 
The connector documentation states that the argument to the callback
function is always a pointer to a struct cn_msg, but rather than encode it
in the API itself, it uses a void pointer everywhere.  This doesn't make
much sense to encode the pointer in documentation as it prevents proper C
type checking from occurring and can easily allow people to use the wrong
pointer type.  So convert the argument type to an explicit struct cn_msg
pointer.

Signed-off-by: Mike Frysinger <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
This commit is contained in:
Mike Frysinger 2009-07-17 10:13:21 -07:00 • committed by David S. Miller
commit 0741241c6b
8 changed files with 16 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

3
drivers/video/uvesafb.c
View file

@ -67,9 +67,8 @@ static DEFINE_MUTEX(uvfb_lock);
* find the kernel part of the task struct, copy the registers and
* the buffer contents and then complete the task.
*/
static void uvesafb_cn_callback(void *data)
static void uvesafb_cn_callback(struct cn_msg *msg)
{
struct cn_msg *msg = data;
struct uvesafb_task *utask;
struct uvesafb_ktask *task;