Home
last modified time | relevance | path

Searched full:creation (Results 1 – 25 of 2193) sorted by relevance

12345678910>>...88

/kernel/linux/linux-6.6/tools/testing/selftests/drivers/net/mlxsw/
Dq_in_q_veto.sh58 check_fail $? "$netdev_proto vlan upper creation on top of an $bridge_proto bridge not rejected"
63 …check_err $? "$netdev_proto vlan upper creation on top of an $bridge_proto bridge rejected without…
76 check_fail $? "802.1ad vlan upper creation on top of a front panel not rejected"
81 check_err $? "802.1ad vlan upper creation on top of a front panel rejected without extack"
99 check_fail $? "802.1ad vlan upper creation on top of a bridge port not rejected"
104 check_err $? "802.1ad vlan upper creation on top of a bridge port rejected without extack"
121 check_fail $? "802.1ad vlan upper creation on top of a lag not rejected"
126 check_err $? "802.1ad vlan upper creation on top of a lag rejected without extack"
166 check_fail $? "vlan upper creation on top of front panel enslaved to 802.1ad bridge not rejected"
170 …check_err $? "vlan upper creation on top of front panel enslaved to 802.1ad bridge rejected withou…
[all …]
/kernel/linux/linux-6.6/Documentation/ABI/testing/
Dconfigfs-most59 creation of the link. In case of speculative
60 configuration, the creation is post-poned until
114 creation of the link. In case of speculative
115 configuration, the creation is post-poned until
169 creation of the link. In case of speculative
170 configuration, the creation is post-poned until
235 creation of the link. In case of speculative
236 configuration, the creation is post-poned until
Devm24 0 Enable HMAC validation and creation
28 creation is enabled (deprecated).
36 will enable HMAC validation and creation
43 HMAC creation and disable all further modification of policy.
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dconfigfs-most59 creation of the link. In case of speculative
60 configuration, the creation is post-poned until
114 creation of the link. In case of speculative
115 configuration, the creation is post-poned until
169 creation of the link. In case of speculative
170 configuration, the creation is post-poned until
235 creation of the link. In case of speculative
236 configuration, the creation is post-poned until
Devm23 0 Enable HMAC validation and creation
27 creation is enabled.
35 will enable HMAC validation and creation
42 HMAC creation and disable all further modification of policy.
/kernel/linux/linux-6.6/tools/testing/selftests/damon/
Ddebugfs_duplicate_context_creation.sh6 # Test duplicated context creation
11 echo "context creation failed"
17 echo "duplicate context creation success"
/kernel/linux/linux-6.6/Documentation/networking/
Dalias.rst16 Alias creation
19 Alias creation is done by 'magic' interface naming: eg. to create a
24 ~~ -> request alias #0 creation (if not yet exists) for eth0
/kernel/linux/linux-5.10/Documentation/networking/
Dalias.rst16 Alias creation
19 Alias creation is done by 'magic' interface naming: eg. to create a
24 ~~ -> request alias #0 creation (if not yet exists) for eth0
/kernel/liteos_a/kernel/include/
Dlos_task.h74 * Task error code: Insufficient memory for task creation.
78 * Solution: Allocate bigger memory partition to task creation.
498 * Define the structure of the parameters used for task creation.
500 * Information of specified parameters passed in during task creation.
572 …* <li>During task creation, the task control block and task stack of the task that is previously a…
588 * @param initParam [IN] Type #TSK_INIT_PARAM_S * Parameter for task creation.
598 * @retval #LOS_ERRNO_TSK_NO_MEMORY Insufficient memory for task creation.
618 …* <li>During task creation, the task control block and task stack of the task that is previously a…
633 * @param initParam [IN] Type #TSK_INIT_PARAM_S * Parameter for task creation.
643 * @retval #LOS_ERRNO_TSK_NO_MEMORY Insufficient memory for task creation.
[all …]
/kernel/linux/linux-5.10/Documentation/filesystems/
Ddirectory-locking.rst19 2) object creation. Locking rules: same as above, but the lock is taken
36 5) link creation. Locking rules:
104 Thus link creation can't be a part of deadlock - it can't be
128 These operations are guaranteed to avoid loop creation. Indeed,
132 would have to exist before rename(). I.e. at the moment of loop creation
/kernel/linux/linux-6.6/Documentation/filesystems/
Ddirectory-locking.rst19 2) object creation. Locking rules: same as above, but the lock is taken
36 5) link creation. Locking rules:
104 Thus link creation can't be a part of deadlock - it can't be
128 These operations are guaranteed to avoid loop creation. Indeed,
132 would have to exist before rename(). I.e. at the moment of loop creation
/kernel/linux/linux-5.10/Documentation/admin-guide/sysctl/
Duser.rst24 The creation of per user per user namespace objects are charged to
28 The creation of objects is also charged to all of the users
29 who created user namespaces the creation of the object happens
/kernel/linux/linux-6.6/Documentation/admin-guide/sysctl/
Duser.rst24 The creation of per user per user namespace objects are charged to
28 The creation of objects is also charged to all of the users
29 who created user namespaces the creation of the object happens
/kernel/linux/linux-6.6/drivers/gpu/drm/msm/disp/dpu1/
Ddpu_rm.c125 DPU_ERROR("failed lm object creation: err %d\n", rc); in dpu_rm_init()
138 DPU_ERROR("failed merge_3d object creation: err %d\n", in dpu_rm_init()
152 DPU_ERROR("failed pingpong object creation: err %d\n", in dpu_rm_init()
168 DPU_ERROR("failed intf object creation: err %d\n", rc); in dpu_rm_init()
181 DPU_ERROR("failed wb object creation: err %d\n", rc); in dpu_rm_init()
194 DPU_ERROR("failed ctl object creation: err %d\n", rc); in dpu_rm_init()
207 DPU_ERROR("failed dspp object creation: err %d\n", rc); in dpu_rm_init()
224 DPU_ERROR("failed dsc object creation: err %d\n", rc); in dpu_rm_init()
237 DPU_ERROR("failed sspp object creation: err %d\n", rc); in dpu_rm_init()
/kernel/linux/linux-6.6/drivers/gpu/drm/i915/
Di915_file_private.h52 * on active contexts. This works by delaying the creation of the
73 * @proto_context_lock, including context creation. Yes, this
74 * means context creation now takes a giant global lock but it
/kernel/linux/linux-5.10/drivers/message/fusion/lsi/
Dmpi_log_sas.h230 /* Creation of duplicate volume attempted (Bus/Target ID checked) */
232 /* Creation failed due to maximum number of supported volumes exceeded */
234 /* Creation failed due to DMA error in trying to read from host */
236 /* Creation failed due to invalid volume type passed down */
238 /* Creation failed due to error reading MFG Page 4 */
240 /* Creation failed when trying to create internal structures */
262 /* Creation failed due to DMA error in trying to read from host */
264 /* Creation failed due to invalid Bus TargetID passed down */
266 /* Creation failed due to error in creating RAID Phys Disk Config Page */
/kernel/linux/linux-6.6/drivers/message/fusion/lsi/
Dmpi_log_sas.h230 /* Creation of duplicate volume attempted (Bus/Target ID checked) */
232 /* Creation failed due to maximum number of supported volumes exceeded */
234 /* Creation failed due to DMA error in trying to read from host */
236 /* Creation failed due to invalid volume type passed down */
238 /* Creation failed due to error reading MFG Page 4 */
240 /* Creation failed when trying to create internal structures */
262 /* Creation failed due to DMA error in trying to read from host */
264 /* Creation failed due to invalid Bus TargetID passed down */
266 /* Creation failed due to error in creating RAID Phys Disk Config Page */
/kernel/linux/linux-6.6/Documentation/scsi/
Dscsi_fc_transport.rst212 - Creation with the kernel and LLDD. This means all transport and
220 Vport Creation.
339 cause the creation of the new attributes on the fc_host. As part of
345 Vport Creation:
356 If "false", the vport is to be enabled upon creation.
366 As mentioned above, vport creation is divided into two parts:
368 - Creation with the kernel and LLDD. This means all transport and
378 vport creation (data structure build up) before returning. We do not
383 This is consistent with the link bouncing post vport creation.
455 any way. (see Vport Creation and the 2 part instantiation discussion).
[all …]
/kernel/linux/linux-5.10/Documentation/scsi/
Dscsi_fc_transport.rst212 - Creation with the kernel and LLDD. This means all transport and
220 Vport Creation.
339 cause the creation of the new attributes on the fc_host. As part of
345 Vport Creation:
356 If "false", the vport is to be enabled upon creation.
366 As mentioned above, vport creation is divided into two parts:
368 - Creation with the kernel and LLDD. This means all transport and
378 vport creation (data structure build up) before returning. We do not
383 This is consistent with the link bouncing post vport creation.
455 any way. (see Vport Creation and the 2 part instantiation discussion).
[all …]
/kernel/linux/linux-6.6/sound/core/
Dpcm_iec958.c25 * Drivers may wish to tweak the contents of the buffer after creation.
172 * Drivers may wish to tweak the contents of the buffer after creation.
198 * Drivers may wish to tweak the contents of the buffer after creation.
/kernel/liteos_m/arch/xtensa/lx6/gcc/
Dlos_arch_interrupt.h118 * Hardware interrupt error code: Insufficient interrupt resources for hardware interrupt creation.
158 * Hardware interrupt error code: Incorrect interrupt creation mode.
162 * Solution: The interrupt creation mode can be only set to OS_HWI_MODE_COMM or OS_HWI_MODE_FAST.
/kernel/linux/linux-6.6/include/video/
Dkyro.h43 * Added the follow IOCTLS for the creation of overlay services...
56 * for the creation of overlay surfaces and setting the video mode.
/kernel/linux/linux-6.6/tools/testing/selftests/bpf/prog_tests/
Ddeny_namespace.c29 * positive return value -> userns creation failed
30 * 0 -> userns creation succeeded
/kernel/linux/linux-5.10/include/video/
Dkyro.h55 * Added the follow IOCTLS for the creation of overlay services...
68 * for the creation of overlay surfaces and setting the video mode.
/kernel/liteos_m/arch/risc-v/nuclei/gcc/
Dlos_arch_interrupt.h92 * Hardware interrupt error code: Insufficient interrupt resources for hardware interrupt creation.
132 * Hardware interrupt error code: Incorrect interrupt creation mode.
136 …* Solution: The interrupt creation mode can be only set to ECLIC_NON_VECTOR_INTERRUPT or ECLIC_VEC…

12345678910>>...88