On Tue, 2007-06-26 at 09:33 -0400, jamal wrote: > On Tue, 2007-26-06 at 00:40 +0200, Johannes Berg wrote: > > > I wonder if we should hold off on this API until we've worked out the > > multicast issue. > > I think we can fix all the code in one shot later. Yes, we could fix the code in the kernel, but since the family ID is dynamically assigned and I'm trying to decouple the multicast group ID from the family ID that would break userspace relying on family==multicast group unless we somehow reserved the family ID number ACPI got to make sure that ACPI gets the same multicast group ID. Combined with the fact that ACPI might be modular and get into generic netlink late in the game this seems non-trivial; also I think it's not necessary since holding off on this ACPI genetlink multicast user (which is the first besides the controller!) until we've worked out the patch shouldn't hurt much. > I just glanced at > your patch but i have to run out, i will stare at it later - seems to be > in the right direction. Thanks. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
