| /linux/Documentation/userspace-api/netlink/ |
| H A D | genetlink-legacy.rst | 4 Netlink specification support for legacy Generic Netlink families 8 required to describe older Generic Netlink families which form 31 New Netlink families should use ``multi-attr`` to define arrays. 32 Older families (e.g. ``genetlink`` control family) attempted to 95 Netlink families should have instead defined this as a flat structure, 107 Modern families use the ``unified`` message ID model, which uses 186 Legacy families can define C structures both to be used as the contents of 272 Legacy families also use ``binary`` attributes to encapsulate C arrays. The 286 New Netlink families should never respond to a DO operation with multiple
|
| H A D | intro.rst | 253 about other families (``CTRL_CMD_GETFAMILY``). 259 call would make the kernel respond with information about *all* the families 352 families, selecting the recipient family on message-by-message basis using 447 notifications about registered families. When a new family is added the 531 families may, however, require a larger buffer. 32kB buffer is recommended 553 Families section in Classic Netlink 556 Netlink refers to subsystems as families. This is a remnant of using 557 sockets and the concept of protocol families, which are part of message 561 as "families" making the term very confusing: 567 struct nlmsghdr), yet it also calls its users "Families". [all …]
|
| /linux/Documentation/core-api/ |
| H A D | netlink.rst | 15 Older families often define "null" attributes and commands with value 17 but should be avoided in new families. The ``unspec`` enum values are 33 Older families do not reply to all of the commands, especially NEW / ADD 73 New families should use ``per-op`` (default) to be able to narrow down the 84 Accept strings without the null-termination (for legacy families only).
|
| /linux/drivers/pinctrl/intel/ |
| H A D | pinctrl-tangier.h | 64 * @families: Array of families this pinctrl handles 65 * @nfamilies: Number of families in the array 80 const struct tng_family *families; member
|
| /linux/tools/testing/selftests/bpf/prog_tests/ |
| H A D | cls_redirect.c | 340 int families[] = { AF_INET, AF_INET6 }; in test_cls_redirect_common() local 345 int servers[__NR_KIND][ARRAY_SIZE(families)] = {}; in test_cls_redirect_common() 346 int conns[__NR_KIND][ARRAY_SIZE(families)] = {}; in test_cls_redirect_common() 347 struct tuple tuples[__NR_KIND][ARRAY_SIZE(families)]; in test_cls_redirect_common() 350 for (i = 0; i < ARRAY_SIZE(families); i++) { in test_cls_redirect_common() 351 slen = prepare_addr(&ss, families[i]); in test_cls_redirect_common() 370 for (j = 0; j < ARRAY_SIZE(families); j++) { in test_cls_redirect_common()
|
| /linux/Documentation/devicetree/bindings/interrupt-controller/ |
| H A D | intel,ixp4xx-interrupt.yaml | 19 The distinct IXP4xx families with different interrupt controller 21 families were the only ones to reach the developer and consumer
|
| /linux/Documentation/arch/sh/ |
| H A D | register-banks.rst | 10 The SH-3 and SH-4 CPU families traditionally include a single partial register 11 bank (selected by SR.RB, only r0 ... r7 are banked), whereas other families
|
| /linux/drivers/net/ethernet/smsc/ |
| H A D | Kconfig | 79 tristate "SMSC LAN911x/LAN921x families embedded ethernet support" 85 Say Y here if you want support for SMSC LAN911x and LAN921x families
|
| /linux/include/uapi/linux/ |
| H A D | atmbr2684.h | 51 * This is for the ATM_NEWBACKENDIF call - these are like socket families: 78 * This is for the ATM_SETBACKEND call - these are like socket families:
|
| H A D | atmppp.h | 16 * This is for the ATM_SETBACKEND call - these are like socket families:
|
| /linux/Documentation/netlink/specs/ |
| H A D | nlctrl.yaml | 9 families registered in the kernel (including itself). 173 doc: Get / dump genetlink families
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | vmscape.rst | 16 The following CPU families are affected by VMSCAPE: 27 - Zen series (families 0x17, 0x19, 0x1a)
|
| /linux/Documentation/sphinx/ |
| H A D | kerneldoc-preamble.sty | 217 due to the lack of suitable font families and/or the texlive-xecjk 221 font families along with the texlive-xecjk package by following 224 Having optional non-variable ``Noto Serif CJK'' font families will
|
| /linux/net/dsa/ |
| H A D | Kconfig | 108 tristate "Tag driver for Microchip 8795/937x/9477/9893 families of switches" 111 Microchip 8795/937x/9477/9893 families of switches.
|
| /linux/tools/net/ynl/pyynl/ |
| H A D | cli.py | 57 spec_group.add_argument('--list-families', action='store_true', 58 help='list all netlink families supported by YNL (has spec)')
|
| /linux/arch/arm/mach-mstar/ |
| H A D | Kconfig | 11 Support for newer MStar/Sigmastar SoC families that are
|
| /linux/arch/arm/mach-ixp4xx/ |
| H A D | ixp4xx-of.c | 8 * We handle 4 different SoC families. These compatible strings are enough
|
| /linux/net/atm/ |
| H A D | Makefile | 3 # Makefile for the ATM Protocol Families.
|
| /linux/drivers/nfc/nxp-nci/ |
| H A D | Kconfig | 7 NPC300 (PN548) or PN7150 families.
|
| /linux/drivers/mtd/lpddr/ |
| H A D | Kconfig | 19 families of devices. This serves similar purpose of CFI on legacy
|
| /linux/drivers/net/wireless/ti/wlcore/ |
| H A D | Kconfig | 8 hardware-specific differences among different chipset families.
|
| /linux/Documentation/arch/arm/sti/ |
| H A D | overview.rst | 21 All the files for multiple machine families (STiH407, STiH410, and STiH418)
|
| /linux/Documentation/arch/arm/stm32/ |
| H A D | overview.rst | 23 All the files for multiple machine families are located in the platform code
|
| /linux/Documentation/devicetree/bindings/iio/dac/ |
| H A D | adi,ad5764.yaml | 7 title: Analog Devices AD5744 and AD5764 DAC families
|
| /linux/include/linux/ |
| H A D | marvell_phy.h | 37 /* These Ethernet switch families contain embedded PHYs, but they do
|