Gregory Nutt e81f279315 Networking: Modify event list handling: Now there are two event lists each device structure: (1) One is for ARP and ICMP data related evetns, the other is for device related events. Callback allocation/free routines no accept a device paramter as well as a list: If the device paramter is added, then the callback goes into both the connection-related liast AND the device event list. Thus each socket type can received both custom data-related events as well as common device related events.

2015-05-28 12:01:38 -06:00

..

icmpv6_advertise.c

…

icmpv6_autoconfig.c

…

icmpv6_input.c

Networking: Modify event list handling: Now there are two event lists each device structure: (1) One is for ARP and ICMP data related evetns, the other is for device related events. Callback allocation/free routines no accept a device paramter as well as a list: If the device paramter is added, then the callback goes into both the connection-related liast AND the device event list. Thus each socket type can received both custom data-related events as well as common device related events.

2015-05-28 12:01:38 -06:00

icmpv6_neighbor.c

…

icmpv6_notify.c

…

icmpv6_ping.c

…

icmpv6_poll.c

Networking: Modify event list handling: Now there are two event lists each device structure: (1) One is for ARP and ICMP data related evetns, the other is for device related events. Callback allocation/free routines no accept a device paramter as well as a list: If the device paramter is added, then the callback goes into both the connection-related liast AND the device event list. Thus each socket type can received both custom data-related events as well as common device related events.

2015-05-28 12:01:38 -06:00

icmpv6_radvertise.c

…

icmpv6_rnotify.c

…

icmpv6_rsolicit.c

…

icmpv6_solicit.c

…

icmpv6.h

Networking: Modify event list handling: Now there are two event lists each device structure: (1) One is for ARP and ICMP data related evetns, the other is for device related events. Callback allocation/free routines no accept a device paramter as well as a list: If the device paramter is added, then the callback goes into both the connection-related liast AND the device event list. Thus each socket type can received both custom data-related events as well as common device related events.

2015-05-28 12:01:38 -06:00

Kconfig

…

Make.defs

…