From: Steven Whitehouse <[EMAIL PROTECTED]>
Date: Wed, 9 Aug 2006 09:01:39 +0100

> Is there anything to stop me using RTNLGRP_NOP3 for that? (suitable
> renamed of course!) So far as I can see its never been assigned to
> anything else...

I have no objection to you using it.

These nops exist because the table used to be a bunch of bitmask
defines instead of the present enum:

#define RTMGRP_LINK             1
#define RTMGRP_NOTIFY           2
#define RTMGRP_NEIGH            4
#define RTMGRP_TC               8

#define RTMGRP_IPV4_IFADDR      0x10
#define RTMGRP_IPV4_MROUTE      0x20
#define RTMGRP_IPV4_ROUTE       0x40

#define RTMGRP_IPV6_IFADDR      0x100
#define RTMGRP_IPV6_MROUTE      0x200
#define RTMGRP_IPV6_ROUTE       0x400

#define RTMGRP_DECnet_IFADDR    0x1000
#define RTMGRP_DECnet_ROUTE     0x4000

That is from 2.4.x
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to