You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When working through the constants in socket for typeshed, I found that these appear to be obsolete:
NETLINK_ARPD: int# linux 2.0 to 2.6.12 (EOL August 2005)NETLINK_ROUTE6: int# linux 2.2 to 2.6.12 (EOL August 2005)NETLINK_SKIP: int# linux 2.0 to 2.6.12 (EOL August 2005)NETLINK_TAPBASE: int# linux 2.2 to 2.6.12 (EOL August 2005)NETLINK_TCPDIAG: int# linux 2.6.0 to 2.6.13 (EOL December 2005)NETLINK_W1: int# linux 2.6.13 to 2.6.17 (EOL October 2006)
The netlink constants are defined in include/linux/netlink.h on linux 2.0 to 3.6. Starting in 3.7 they moved to include/uapi/linux/netlink.h. I've annotated these with the versions of linux where I was able to find them, and confirmed that they're not present in FreeBSD's Netlink implementation either.
I suspect these can be safely removed, but I'm not terribly familiar with Netlink myself.
Has this already been discussed elsewhere?
This is a minor feature, which does not need previous discussion elsewhere
Links to previous discussion of this feature:
No response
The text was updated successfully, but these errors were encountered:
Feature or enhancement
Proposal:
When working through the constants in
socket
for typeshed, I found that these appear to be obsolete:The netlink constants are defined in
include/linux/netlink.h
on linux 2.0 to 3.6. Starting in 3.7 they moved toinclude/uapi/linux/netlink.h
. I've annotated these with the versions of linux where I was able to find them, and confirmed that they're not present in FreeBSD's Netlink implementation either.I suspect these can be safely removed, but I'm not terribly familiar with Netlink myself.
Has this already been discussed elsewhere?
This is a minor feature, which does not need previous discussion elsewhere
Links to previous discussion of this feature:
No response
The text was updated successfully, but these errors were encountered: