I think @vmaffione would be the responsible one for these functions? But, why not just make this a void, too, since it only is called in one place and the return value is never checked there.

I think @vmaffione would be the responsible one for these functions? But, why not just make this a void, too, since it only is called in one place and the return value is never checked there.

I considered that, but wanted to defer. The other option is that if the driver wants to explicitly ignore the return value it could use '(void)' when calling the function which might also quiet the compiler complaint.

I would prefer to leave the return value as an int, even if the return value is not used right now by this particular driver. It's a matter of uniformity within netmap (RX counterpart, other drivers, Linux drivers, etc.).
If this change is meant to suppress a compiler warning, I think the best would be for iflib to explicitly cast the return value to void, as @jhb suggests.