| /linux/fs/xfs/libxfs/ |
| H A D | xfs_inode_util.h | 22 * according to accepted Unix behaviors, callers must initialize idmap to the
23 * correct idmapping structure to get the correct inheritance behaviors when
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-devlink | 124 '0' means the device link can affect other device behaviors
130 up and doesn't not affect other behaviors of the devices.
|
| /linux/arch/m68k/include/asm/ |
| H A D | switch_to.h | 15 * and so we might get see unexpected behaviors when a task returns
|
| /linux/tools/testing/selftests/net/packetdrill/ |
| H A D | tcp_dsack_mult.pkt | 2 // Test various DSACK (RFC 2883) behaviors.
|
| /linux/Documentation/process/ |
| H A D | code-of-conduct.rst | 51 contributor for other behaviors that they deem inappropriate, threatening,
|
| /linux/Documentation/devicetree/bindings/display/mediatek/ |
| H A D | mediatek,padding.yaml | 19 register must be cleared to 0, or undefined behaviors could happen.
|
| /linux/tools/testing/selftests/ublk/ |
| H A D | fault_inject.c | 5 * testing specific behaviors of ublk_drv. Currently is a null target
|
| /linux/tools/testing/selftests/net/ |
| H A D | srv6_end_flavors_test.sh | 11 # or extend the existing SRv6 End, End.X and End.T behaviors. For the sake of
17 # The End, End.X, and End.T behaviors can support these flavors either
37 # SR node, it will be active only on such behaviors bound to a penultimate SID
502 # (i.e. behaviors) that each of them needs to perform. Every <nodeid:op>
|
| H A D | srv6_hl2encap_red_l2vpn_test.sh | 346 # Endpoint behaviors instances are grouped together in the 'localsid'
357 # $3 - SRv6 routers configured for steering traffic (End behaviors)
593 # - rt-4,rt-3 (SRv6 End behaviors)
|
| H A D | srv6_hencap_red_l3vpn_test.sh | 431 # $3 - SRv6 routers configured for steering traffic (End behaviors)
621 # - rt-3,rt-4 (SRv6 End behaviors)
637 # - rt-4,rt-3 (SRv6 End behaviors)
|
| /linux/drivers/hid/bpf/progs/ |
| H A D | README | 4 fix some behaviors without being entirely mandatory. It is better to load them
|
| /linux/tools/perf/Documentation/ |
| H A D | Build.txt | 67 supported by GCC. UBSan detects undefined behaviors of programs at runtime.
|
| H A D | perf-kvm.txt | 31 perf.data.host, please input --host --no-guest. The behaviors are shown as
|
| /linux/Documentation/block/ |
| H A D | pr.rst | 18 These behaviors are optional in SPC but will be automatically applied
|
| /linux/drivers/gpu/drm/mediatek/ |
| H A D | mtk_padding.c | 65 * undefined behaviors could happen in mtk_padding_start()
|
| /linux/tools/lib/bpf/ |
| H A D | libbpf_legacy.h | 36 * Disable any libbpf 1.0 behaviors. This is the default before libbpf
|
| /linux/Documentation/bpf/ |
| H A D | map_cgroup_storage.rst | 19 ``BPF_MAP_TYPE_CGROUP_STORAGE`` map type. Some of its behaviors was changed in
|
| /linux/Documentation/locking/ |
| H A D | locktorture.rst | 19 different critical region behaviors. The amount of contention on the lock
|
| /linux/include/uapi/linux/ |
| H A D | i2c.h | 70 * passing certain @flags may have changed those standard protocol behaviors.
|
| /linux/rust/kernel/irq/ |
| H A D | flags.rs | 9 /// Flags can be used to request specific behaviors when registering an IRQ
|
| /linux/drivers/acpi/ |
| H A D | button.c | 273 * trigger unexpected behaviors. in acpi_lid_notify_state()
276 * "close" will trigger unexpected behaviors. in acpi_lid_notify_state()
|
| /linux/drivers/vfio/pci/ |
| H A D | vfio_pci.c | 134 * These behaviors originated in vfio-pci and moved into in vfio_pci_init_dev()
|
| /linux/Documentation/arch/x86/ |
| H A D | amd-hfi.rst | 49 special scheduling behaviors. The below table depicts an example of thread
|
| /linux/Documentation/hid/ |
| H A D | uhid.rst | 130 describes special behaviors of a device. The following flags are defined:
|
| /linux/Documentation/driver-api/usb/ |
| H A D | error-codes.rst | 13 behave the same except for transfer speed dependent behaviors and the
|