Re: [PATCH 1/2] Type-safe ioport callbacks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



 On 10/25/2010 02:54 PM, Juan Quintela wrote:
Avi Kivity<avi@xxxxxxxxxx>  wrote:

>  +static void ioport_writeb_thunk(void *opaque, uint32_t addr, uint32_t data)
>  +{
>  +    IOPort *ioport = opaque;
>  +
>  +    return ioport->ops->writeb(ioport, addr, data);
>  +}
>  +
>  +static void ioport_writew_thunk(void *opaque, uint32_t addr, uint32_t data)
>  +{
>  +    IOPort *ioport = opaque;
>  +
>  +    return ioport->ops->writew(ioport, addr, data);
>  +}
>  +
>  +static void ioport_writel_thunk(void *opaque, uint32_t addr, uint32_t data)
>  +{
>  +    IOPort *ioport = opaque;
>  +
>  +    return ioport->ops->writel(ioport, addr, data);
>  +}

"return" is not needed on this three functions.


Fixed.

--
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux