/linux/mm/kmsan/ |
H A D | core.c | 91 bool backwards; in kmsan_internal_memmove_metadata() local 112 backwards = dst > src; in kmsan_internal_memmove_metadata() 113 step = backwards ? -1 : 1; in kmsan_internal_memmove_metadata() 114 iter = backwards ? n - 1 : 0; in kmsan_internal_memmove_metadata()
|
/linux/Documentation/dev-tools/ |
H A D | checkuapi.rst | 8 checks UAPI header files for userspace backwards-compatibility across 79 All 912 UAPI headers compatible with x86 appear to be backwards compatible 114 error - 1/912 UAPI headers compatible with x86 appear _not_ to be backwards compatible 121 in which the userspace backwards compatibility is ambiguous:: 127 All 912 UAPI headers compatible with x86 appear to be backwards compatible 161 error - 1/912 UAPI headers compatible with x86 appear _not_ to be backwards compatible 178 All 912 UAPI headers compatible with x86 appear to be backwards compatible 199 error - 1/912 UAPI headers compatible with x86 appear _not_ to be backwards compatible 254 error - 1/884 UAPI headers compatible with arm64 appear _not_ to be backwards compatible 336 error - 1/912 UAPI headers compatible with x86 appear _not_ to be backwards compatible [all …]
|
/linux/scripts/ |
H A D | patch-kernel | 97 backwards () { function 231 backwards
|
/linux/Documentation/devicetree/bindings/net/ |
H A D | hisilicon-hns-mdio.txt | 8 while "hisilicon,mdio" is optional for backwards compatibility only on
|
/linux/Documentation/devicetree/bindings/interrupt-controller/ |
H A D | opencores,or1k-pic.txt | 11 but this is only for backwards compatibility.
|
H A D | nvidia,tegra20-ictlr.txt | 13 subsequent SoCs remained backwards-compatible with Tegra30, so on
|
/linux/Documentation/networking/ |
H A D | alias.rst | 10 for backwards compatibility.
|
H A D | netif-msg.rst | 13 constrained by backwards compatibility previous practice. It is useful
|
/linux/net/8021q/ |
H A D | Kconfig | 39 supersedes GVRP and is not backwards-compatible.
|
/linux/Documentation/ABI/testing/ |
H A D | sysfs-bus-rbd | 49 will fail for backwards compatibility reasons. 63 available will fail for backwards compatibility reasons.
|
H A D | sysfs-driver-ppi | 15 A symlink from tpmX/device/ppi to tpmX/ppi to provide backwards
|
/linux/arch/arm64/boot/dts/sprd/ |
H A D | whale2.dtsi | 132 /* For backwards compatibility: */ 280 /* For backwards compatibility: */
|
/linux/Documentation/filesystems/ |
H A D | devpts.rst | 14 To retain backwards compatibility the a ptmx device node (aka any node
|
/linux/arch/arm/boot/dts/intel/pxa/ |
H A D | pxa25x.dtsi | 42 /* For backwards compatibility: */
|
H A D | pxa27x.dtsi | 16 /* For backwards compatibility: */
|
/linux/tools/testing/selftests/livepatch/ |
H A D | README | 35 tested on systems with different kABI, ensuring they the tests are backwards
|
/linux/Documentation/kbuild/ |
H A D | headers_install.rst | 18 Kernel headers are backwards compatible, but not forwards compatible. This
|
/linux/drivers/staging/media/deprecated/atmel/ |
H A D | TODO | 5 not backwards compatible with the current usability of the driver.
|
/linux/Documentation/sound/designs/ |
H A D | timestamping.rst | 35 ``CLOCK_REALTIME`` (NTP corrections including going backwards), 36 ``CLOCK_MONOTONIC`` (NTP corrections but never going backwards), 87 For backwards compatibility with previous implementations that did not
|
/linux/arch/x86/coco/sev/ |
H A D | shared.c | 805 bool backwards) in vc_insn_string_read() argument 807 int i, b = backwards ? -1 : 1; in vc_insn_string_read() 831 bool backwards) in vc_insn_string_write() argument 833 int i, s = backwards ? -1 : 1; in vc_insn_string_write()
|
/linux/Documentation/driver-api/firmware/ |
H A D | firmware-usage-guidelines.rst | 31 backwards compatibility for the older major versions. Minor version
|
/linux/Documentation/driver-api/ |
H A D | zorro.rst | 20 - Zorro III is a 32-bit extension of Zorro II, which is backwards compatible
|
/linux/drivers/mtd/spi-nor/ |
H A D | Kconfig | 41 of your SPI flash. This is only to keep backwards compatibility.
|
/linux/Documentation/bpf/ |
H A D | bpf_design_QA.rst | 313 kernel preserve backwards compatibility for these features? 319 the kernel will preserve backwards compatibility, as they are part of UAPI. 337 In other words, no backwards compatibility is guaranteed if one using a type 343 bpf_obj_new for user defined types). Will the kernel preserve backwards
|
/linux/Documentation/leds/ |
H A D | leds-qcom-lpg.rst | 74 the pattern forward, then backwards. This mode is automatically used by the
|