Searched full:compatibility (Results 1 – 25 of 3604) sorted by relevance
12345678910>>...145
| /kernel/linux/common_modules/ |
| D | OAT.xml | 36 "compatibility" is used to check license compatibility in the specified path;
60 …<policyitem type="compatibility" name="GPL" path="newip/.*" rule="may" group="defaultGroup" filefi…
61 …<policyitem type="compatibility" name="GPL" path="xpm/.*" rule="may" group="defaultGroup" filefilt…
62 …<policyitem type="compatibility" name="GPL" path="memory_security/.*" rule="may" group="defaultGro…
63 …<policyitem type="compatibility" name="GPL" path="qos_auth/.*" rule="may" group="defaultGroup" fil…
64 …<policyitem type="compatibility" name="GPL" path="ucollection/.*" rule="may" group="defaultGroup" …
65 …<policyitem type="compatibility" name="GPL" path="code_sign/.*" rule="may" group="defaultGroup" fi…
66 …<policyitem type="compatibility" name="GPL" path="container_escape_detection/.*" rule="may" group=…
67 …<policyitem type="compatibility" name="GPL" path="tzdriver/.*" rule="may" group="defaultGroup" fil…
68 …<policyitem type="compatibility" name="GPL" path="module_sample/.*" rule="may" group="defaultGroup…
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/ptp/ |
| D | brcm,ptp-dte.txt | 4 - compatible: should contain the core compatibility string
5 and the SoC compatibility string. The SoC
6 compatibility string is to handle SoC specific
8 Core compatibility string:
10 SoC compatibility strings:
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/ptp/ |
| D | brcm,ptp-dte.txt | 4 - compatible: should contain the core compatibility string
5 and the SoC compatibility string. The SoC
6 compatibility string is to handle SoC specific
8 Core compatibility string:
10 SoC compatibility strings:
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/ |
| D | syscall-user-dispatch.rst | 10 Compatibility layers like Wine need a way to efficiently emulate system
22 invoking the kernel, when crossing the compatibility layer API
27 The goal of this design is to provide very quick compatibility layer
29 personality every time the compatibility layer executes. Instead, a
83 Syscall User Dispatch provides functionality for compatibility layers to
|
| /kernel/linux/linux-6.6/include/uapi/linux/ |
| D | route.h | 12 * for the purposes of compatibility only.
40 short rt_metric; /* +1 for binary compatibility! */
44 #define rt_mss rt_mtu /* Compatibility :-( */
58 #define RTF_MSS RTF_MTU /* Compatibility :-( */
|
| D | if.h | 23 #include <linux/libc-compat.h> /* for compatibility with glibc */
39 /* For glibc compatibility. An empty enum does not compile. */
83 /* for compatibility with glibc net/if.h */
110 /* for compatibility with glibc net/if.h */
194 /* for compatibility with glibc net/if.h */
232 /* for compatibility with glibc net/if.h */
284 /* for compatibility with glibc net/if.h */
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | route.h | 12 * for the purposes of compatibility only.
40 short rt_metric; /* +1 for binary compatibility! */
44 #define rt_mss rt_mtu /* Compatibility :-( */
58 #define RTF_MSS RTF_MTU /* Compatibility :-( */
|
| D | if.h | 23 #include <linux/libc-compat.h> /* for compatibility with glibc */
39 /* For glibc compatibility. An empty enum does not compile. */
83 /* for compatibility with glibc net/if.h */
110 /* for compatibility with glibc net/if.h */
194 /* for compatibility with glibc net/if.h */
232 /* for compatibility with glibc net/if.h */
284 /* for compatibility with glibc net/if.h */
|
| /kernel/linux/linux-5.10/drivers/message/fusion/lsi/ |
| D | mpi_log_sas.h | 270 /* Compatibility Error : IR Disabled */
272 /* Compatibility Error : Inquiry Command failed */
274 /* Compatibility Error : Device not direct access device */
276 /* Compatibility Error : Removable device found */
278 /* Compatibility Error : Device SCSI Version not 2 or higher */
280 /* Compatibility Error : SATA device, 48 BIT LBA not supported */
282 /* Compatibility Error : Device does not have 512 byte block sizes */
284 /* Compatibility Error : Volume Type check failed */
286 /* Compatibility Error : Volume Type is unsupported by FW */
288 /* Compatibility Error : Disk drive too small for use in volume */
[all …]
|
| /kernel/linux/linux-6.6/drivers/message/fusion/lsi/ |
| D | mpi_log_sas.h | 270 /* Compatibility Error : IR Disabled */
272 /* Compatibility Error : Inquiry Command failed */
274 /* Compatibility Error : Device not direct access device */
276 /* Compatibility Error : Removable device found */
278 /* Compatibility Error : Device SCSI Version not 2 or higher */
280 /* Compatibility Error : SATA device, 48 BIT LBA not supported */
282 /* Compatibility Error : Device does not have 512 byte block sizes */
284 /* Compatibility Error : Volume Type check failed */
286 /* Compatibility Error : Volume Type is unsupported by FW */
288 /* Compatibility Error : Disk drive too small for use in volume */
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/net/ |
| D | marvell,pp2.yaml | 94 for backward compatibility but shouldn't be used for new
120 Legacy binding for backward compatibility.
216 port-id = <0>; /* For backward compatibility. */
224 port-id = <1>; /* For backward compatibility. */
261 port-id = <0>; /* For backward compatibility. */
280 port-id = <1>; /* For backward compatibility. */
302 port-id = <2>; /* For backward compatibility. */
|
| /kernel/linux/linux-5.10/fs/ext4/ |
| D | Kconfig | 2 # Ext3 configs are here for backward compatibility with old configs which may
9 This config option is here only for backward compatibility. ext3
18 This config option is here only for backward compatibility. ext3
26 This config option is here only for backward compatibility. ext3
|
| /kernel/linux/linux-6.6/drivers/net/ethernet/hisilicon/ |
| D | Kconfig | 104 tristate "Hisilicon HNS3 HCLGE Acceleration Engine & Compatibility Layer Support"
110 compatibility layer. The engine would be used in Hisilicon hip08 family of
123 tristate "Hisilicon HNS3VF Acceleration Engine & Compatibility Layer Support"
128 compatibility layer. The engine would be used in Hisilicon hip08 family of
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/hisilicon/ |
| D | Kconfig | 102 tristate "Hisilicon HNS3 HCLGE Acceleration Engine & Compatibility Layer Support"
107 compatibility layer. The engine would be used in Hisilicon hip08 family of
120 tristate "Hisilicon HNS3VF Acceleration Engine & Compatibility Layer Support"
125 compatibility layer. The engine would be used in Hisilicon hip08 family of
|
| /kernel/linux/linux-6.6/fs/ext4/ |
| D | Kconfig | 2 # Ext3 configs are here for backward compatibility with old configs which may
9 This config option is here only for backward compatibility. ext3
18 This config option is here only for backward compatibility. ext3
26 This config option is here only for backward compatibility. ext3
|
| /kernel/linux/linux-6.6/tools/lib/bpf/ |
| D | bpf.h | 41 size_t sz; /* size of this struct for forward/backward compatibility */
65 size_t sz; /* size of this struct for forward/backward compatibility */
121 size_t sz; /* size of this struct for forward/backward compatibility */
156 size_t sz; /* size of this struct for forward/backward compatibility */
288 size_t sz; /* size of this struct for forward/backward compatibility */
302 size_t sz; /* size of this struct for forward/backward compatibility */
322 size_t sz; /* size of this struct for forward/backward compatibility */
336 size_t sz; /* size of this struct for forward/backward compatibility */
379 size_t sz; /* size of this struct for forward/backward compatibility */
430 size_t sz; /* size of this struct for forward/backward compatibility */
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/Documentation/ |
| D | db-export.txt | 20 backward and forward compatibility, by following some simple rules:
30 backward compatibility by testing for the presence of new tables and columns
33 4. The export scripts themselves maintain forward compatibility (i.e. an existing
|
| /kernel/linux/linux-6.6/tools/perf/Documentation/ |
| D | db-export.txt | 20 backward and forward compatibility, by following some simple rules:
30 backward compatibility by testing for the presence of new tables and columns
33 4. The export scripts themselves maintain forward compatibility (i.e. an existing
|
| /kernel/linux/linux-6.6/include/uapi/asm-generic/ |
| D | resource.h | 8 * ( Compatibility detail: there are architectures that have
10 * to keep that order for binary compatibility. The reasons
55 * Some architectures override this (for compatibility reasons):
|
| /kernel/linux/linux-5.10/include/uapi/asm-generic/ |
| D | resource.h | 8 * ( Compatibility detail: there are architectures that have
10 * to keep that order for binary compatibility. The reasons
55 * Some architectures override this (for compatibility reasons):
|
| /kernel/linux/linux-5.10/tools/lib/bpf/ |
| D | bpf.h | 132 size_t sz; /* size of this struct for forward/backward compatibility */
156 size_t sz; /* size of this struct for forward/backward compatibility */
173 size_t sz; /* size of this struct for forward/backward compatibility */
188 size_t sz; /* size of this struct for forward/backward compatibility */
255 size_t sz; /* size of this struct for forward/backward compatibility */
264 size_t sz; /* size of this struct for forward/backward compatibility */
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/serial/ |
| D | mvebu-uart.txt | 15 compatible string for backward compatibility), it will only work
20 should not be used and are supported only for backward compatibility.
31 - For backward compatibility reasons, a single element interrupts
|
| /kernel/linux/linux-6.6/Documentation/process/ |
| D | adding-syscalls.rst | 269 Compatibility System Calls (Generic)
276 However, there are a couple of situations where a compatibility layer is
290 The second situation that requires a compatibility layer is if one of the
294 32-bit values, which then need to be re-assembled in the compatibility layer.
297 does **not** need a compatibility layer; for example, :manpage:`splice(2)`'s arguments of
300 The compatibility version of the system call is called ``compat_sys_xyzzy()``,
356 Compatibility System Calls (x86)
359 To wire up the x86 architecture of a system call with a compatibility version,
375 the compatibility wrapper::
424 If the system call needs a compatibility layer (as in the previous section)
[all …]
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | adding-syscalls.rst | 269 Compatibility System Calls (Generic)
276 However, there are a couple of situations where a compatibility layer is
290 The second situation that requires a compatibility layer is if one of the
294 32-bit values, which then need to be re-assembled in the compatibility layer.
297 does **not** need a compatibility layer; for example, :manpage:`splice(2)`'s arguments of
300 The compatibility version of the system call is called ``compat_sys_xyzzy()``,
356 Compatibility System Calls (x86)
359 To wire up the x86 architecture of a system call with a compatibility version,
375 the compatibility wrapper::
424 If the system call needs a compatibility layer (as in the previous section)
[all …]
|
| /kernel/linux/linux-5.10/drivers/base/ |
| D | class.c | 496 * class_compat_register - register a compatibility class
499 * Compatibility class are meant as a temporary user-space compatibility
519 * class_compat_unregister - unregister a compatibility class
530 * class_compat_create_link - create a compatibility class device link to
532 * @cls: the compatibility class
548 * backwards compatibility as possible. in class_compat_create_link()
562 * class_compat_remove_link - remove a compatibility class device link to
564 * @cls: the compatibility class
|
12345678910>>...145