Searched full:backwards (Results 1 – 25 of 75) sorted by relevance
123
| /Documentation/dev-tools/ |
| 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 …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | opencores,or1k-pic.txt | 11 but this is only for backwards compatibility.
|
| D | nvidia,tegra20-ictlr.txt | 13 subsequent SoCs remained backwards-compatible with Tegra30, so on
|
| /Documentation/devicetree/bindings/net/ |
| D | hisilicon-hns-mdio.txt | 8 while "hisilicon,mdio" is optional for backwards compatibility only on
|
| /Documentation/filesystems/ |
| D | devpts.rst | 14 To retain backwards compatibility the a ptmx device node (aka any node
|
| D | cramfs.rst | 41 which the timestamp reverts to 1970, i.e. moves backwards in time.
|
| /Documentation/networking/ |
| D | alias.rst | 10 for backwards compatibility.
|
| D | netif-msg.rst | 13 constrained by backwards compatibility previous practice. It is useful
|
| D | vxlan.rst | 36 and uses the Linux-selected value by default to maintain backwards
|
| /Documentation/devicetree/bindings/dma/ |
| D | sifive,fu540-c000-pdma.yaml | 50 description: For backwards-compatibility, the default value is 4
|
| /Documentation/kbuild/ |
| D | headers_install.rst | 18 Kernel headers are backwards compatible, but not forwards compatible. This
|
| /Documentation/driver-api/firmware/ |
| D | firmware-usage-guidelines.rst | 31 backwards compatibility for the older major versions. Minor version
|
| /Documentation/sound/designs/ |
| 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
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-ppi | 15 A symlink from tpmX/device/ppi to tpmX/ppi to provide backwards
|
| D | sysfs-bus-rbd | 49 will fail for backwards compatibility reasons.
63 available will fail for backwards compatibility reasons.
|
| /Documentation/devicetree/bindings/mfd/ |
| D | aspeed,ast2x00-scu.yaml | 83 The reg should be the unique silicon id register, and not backwards
|
| /Documentation/admin-guide/ |
| D | highuid.rst | 25 - Decide whether or not to keep backwards compatibility with the system
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | bq24735.yaml | 32 Note: for backwards compatibility reasons, the GPIO must be active on AC adapter
|
| /Documentation/devicetree/bindings/i2c/ |
| D | opencores,i2c-ocores.yaml | 44 This is to keep backwards compatibility with setups using old DTB. i2c bus
|
| /Documentation/process/ |
| D | programming-language.rst | 40 small changes to the language that are not backwards compatible.
|
| /Documentation/driver-api/ |
| D | zorro.rst | 20 - Zorro III is a 32-bit extension of Zorro II, which is backwards compatible
|
| /Documentation/leds/ |
| D | leds-qcom-lpg.rst | 74 the pattern forward, then backwards. This mode is automatically used by the
|
| D | well-known-leds.txt | 9 Anyway, if backwards compatibility is not an issue, new code should
|
| /Documentation/bpf/ |
| 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
|
| /Documentation/core-api/ |
| D | timekeeping.rst | 39 for internal uses, since it can jump backwards due to a leap
|
123