From owner-cvs-all  Mon Dec 14 00:25:49 1998
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA23053
          for cvs-all-outgoing; Mon, 14 Dec 1998 00:25:49 -0800 (PST)
          (envelope-from owner-cvs-all@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA23019
          for <committers@FreeBSD.ORG>; Mon, 14 Dec 1998 00:25:45 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA12436;
	Mon, 14 Dec 1998 19:25:37 +1100
Date: Mon, 14 Dec 1998 19:25:37 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199812140825.TAA12436@godzilla.zeta.org.au>
To: committers@FreeBSD.ORG, dillon@apollo.backplane.com
Subject: Re: best way to fix function mismatch warning
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk

>    This warning occurs because the vxintr function does not match the
>    function type expected by pci_map_int.  That is, because pci_map_int
>    expects a void func(void *) function and vxintr is a 
>    void func(struct softc *).
>
>    So, to get rid of the warning do we (a) cast the function pointer
>    in the pci_map_int() call to the correct type or (b) make the function

No, this would just break the warning.  The warning is already broken in
if_vx_eisa.c.

>    (in  dev/vx/*) take a void * and then reassign the variable to a pointer
>    of the right type inside it?

Why not?  It really does take a void *.

>Or (c) some other choice that I haven't
>    thought of ?

cvs remove ;-).

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message