> So there is no reason we have to use any particular type for the > IGMPv3/MLDv2 interfaces provided by the kernel, we can use whatever > types we want. "whatever you want"... I think your statement seems a little strange, but, ... ok, as you want. Anyway, so, what is the benefit to use __u32 for the members of "struct ip_mreq_source", even though "struct ip_mreq" uses in_addr? Such __u32 definition makes application programmers confuse and use "#ifdef Linux" or "#ifndef Linux" stuff in their codes. What is your favor? -- Hitoshi Asaeda - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
