summaryrefslogtreecommitdiffstats
path: root/Modules/_cursesmodule.c
diff options
context:
space:
mode:
authorkarl ding <karlding@users.noreply.github.com>2019-07-31 08:47:16 (GMT)
committerƁukasz Langa <lukasz@langa.pl>2019-07-31 08:47:16 (GMT)
commit31c4fd2a10d90beaa37d630e5f74a471e14e089d (patch)
tree40a7a11d67b92d2ea4a2eca25361ea36d2aa4935 /Modules/_cursesmodule.c
parent472eced6770c2fabab3031e4e16cd32e32b8a0cc (diff)
downloadcpython-31c4fd2a10d90beaa37d630e5f74a471e14e089d.zip
cpython-31c4fd2a10d90beaa37d630e5f74a471e14e089d.tar.gz
cpython-31c4fd2a10d90beaa37d630e5f74a471e14e089d.tar.bz2
bpo-37085: Expose SocketCAN bcm_msg_head flags (#13646)
Expose the CAN_BCM SocketCAN constants used in the bcm_msg_head struct flags (provided by <linux/can/bcm.h>) under the socket library. This adds the following constants with a CAN_BCM prefix: * SETTIMER * STARTTIMER * TX_COUNTEVT * TX_ANNOUNCE * TX_CP_CAN_ID * RX_FILTER_ID * RX_CHECK_DLC * RX_NO_AUTOTIMER * RX_ANNOUNCE_RESUME * TX_RESET_MULTI_IDX * RX_RTR_FRAME * CAN_FD_FRAME The CAN_FD_FRAME flag was introduced in the 4.8 kernel, while the other ones were present since SocketCAN drivers were mainlined in 2.6.25. As such, it is probably unnecessary to guard against these constants being missing.
Diffstat (limited to 'Modules/_cursesmodule.c')
0 files changed, 0 insertions, 0 deletions