diff options
author | 2009-07-17 10:13:21 -0700 | |
---|---|---|
committer | 2009-07-17 10:13:21 -0700 | |
commit | 0741241c6b80bfd58417e95de984d60c9e9ef2a0 (patch) | |
tree | 9fa70e5e918e0735c531988f64b92cb5655baf28 /drivers/video/uvesafb.c | |
parent | tun: Allow tap device to send/receive UFO packets. (diff) | |
download | linux-0741241c6b80bfd58417e95de984d60c9e9ef2a0.tar.gz linux-0741241c6b80bfd58417e95de984d60c9e9ef2a0.tar.bz2 linux-0741241c6b80bfd58417e95de984d60c9e9ef2a0.zip |
connector: make callback argument type explicit
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 <vapier@gentoo.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/video/uvesafb.c')
-rw-r--r-- | drivers/video/uvesafb.c | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/drivers/video/uvesafb.c b/drivers/video/uvesafb.c index ca5b4643a401..e98baf6916b8 100644 --- a/drivers/video/uvesafb.c +++ b/drivers/video/uvesafb.c @@ -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; |