/* * netsniff-ng - the packet sniffing beast * Copyright 2009, 2010 Daniel Borkmann. * Copyright 2014, 2015 Tobias Klauser * Subject to the GPL, version 2. */ #ifndef LOOKUP_H #define LOOKUP_H enum lookup_type { LT_PORTS_UDP, LT_PORTS_TCP, LT_ETHERTYPES, LT_OUI, LT_MAX, }; extern void lookup_init(enum lookup_type which); extern void lookup_cleanup(enum lookup_type which); extern const char *lookup_port_udp(unsigned int id); extern const char *lookup_port_tcp(unsigned int id); extern const char *lookup_ether_type(unsigned int id); extern const char *lookup_vendor(unsigned int id); static inline const char *lookup_vendor_str(unsigned int id) { return lookup_vendor(id) ? : "Unknown"; } #endif /* LOOKUP_H */ in'>index : net-next.git
net-next plumbingsTobias Klauser
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJohannes Berg <johannes.berg@intel.com>2017-01-02 16:01:57 +0100
committerJohannes Berg <johannes.berg@intel.com>2017-01-24 11:07:35 +0100
commit1331b62c97217459780e040e8a66bb609f2acd20 (patch)
treef06688ed329f86dcfaa462582681f9156fca16f3
parent57eeb2086d6477968990e1790a9d8d0ec7ee8a4d (diff)
rfkill: remove rfkill-regulator
There are no users of this ("vrfkill") in the tree, so it's just dead code - remove it. This also isn't really how rfkill is supposed to be used - it's intended as a signalling mechanism to/from the device, which the driver (and partially cfg80211) will handle - having a separate rfkill instance for a regulator is confusing, the driver should use the regulator instead to turn off the device when requested. Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat