Home
last modified time | relevance | path

Searched refs:explicit (Results 1 – 25 of 209) sorted by relevance

123456789

/linux-6.12.1/drivers/target/
Dtarget_core_alua.c33 int *primary, int explicit);
35 struct se_lun *lun, int explicit, int offline);
728 core_alua_check_transition(int state, int valid, int *primary, int explicit) in core_alua_check_transition() argument
770 if (!(valid & ALUA_T_SUP) || explicit) in core_alua_check_transition()
979 int explicit) in core_alua_do_transition_tg_pt() argument
990 if (explicit && new_state == ALUA_ACCESS_STATE_TRANSITION) { in core_alua_do_transition_tg_pt()
1001 tg_pt_gp->tg_pt_gp_alua_access_status = (explicit) ? in core_alua_do_transition_tg_pt()
1040 " from primary access state %s to %s\n", (explicit) ? "explicit" : in core_alua_do_transition_tg_pt()
1058 int explicit) in core_alua_do_port_transition() argument
1071 explicit) != 0) in core_alua_do_port_transition()
[all …]
/linux-6.12.1/Documentation/RCU/
Dlockdep.rst41 Use explicit check expression "c" along with
45 Use explicit check expression "c" along with
49 Use explicit check expression "c" along with
53 Use explicit check expression "c" along with
61 Use explicit check expression "c", and omit all barriers
/linux-6.12.1/Documentation/devicetree/bindings/sound/
Dtdm-slot.txt18 to specify an explicit mapping of the channels and the slots. If it's absent
26 The explicit masks are given as array of integers, where the first
/linux-6.12.1/Documentation/locking/
Dpreempt-locking.rst15 requires explicit additional locking for very few additional situations.
21 RULE #1: Per-CPU data structures need explicit protection
32 First, since the data is per-CPU, it may not have explicit SMP locking, but
132 in doubt, rely on locking or explicit preemption disabling.
/linux-6.12.1/include/trace/events/
Dblock.h449 TP_PROTO(struct request_queue *q, unsigned int depth, bool explicit),
451 TP_ARGS(q, depth, explicit),
477 TP_PROTO(struct request_queue *q, unsigned int depth, bool explicit),
479 TP_ARGS(q, depth, explicit)
/linux-6.12.1/tools/memory-model/litmus-tests/
DLB+poonceonces.litmus7 * be prevented even with no explicit ordering?
/linux-6.12.1/arch/arm64/boot/dts/amlogic/
Dmeson-g12a-fbx8am-realtek.dtso20 /* No explicit compatible for rtl8822cs sdio */
/linux-6.12.1/net/netlabel/
DKconfig12 NetLabel provides support for explicit network packet labeling
/linux-6.12.1/
DCOPYING10 With an explicit syscall exception, as stated at:
/linux-6.12.1/Documentation/userspace-api/
Ddma-buf-alloc-exchange.rst27 format and modifier (implicit or explicit).
332 ``DRM_FORMAT_MOD_LINEAR``, which is an explicit guarantee that the image
340 as the sole member of a modifier list to declare that explicit modifiers are
345 at all) to declare that explicit modifiers are not supported and must not be
350 that the underlying layout is implementation-defined and that an explicit
357 not been allocated with an explicit modifier
361 explicit. For example, if a user wishes to allocate a buffer for use between
363 user **must not** allocate the buffer with explicit modifiers and attempt to
369 to explicit modifiers. For example, if the buffer is allocated with
371 ``gbm_bo_get_modifier`` and then use this modifier as an explicit modifier token
/linux-6.12.1/Documentation/devicetree/bindings/mtd/partitions/
Dbrcm,bcm963xx-imagetag.txt6 needs to be used with an explicit firmware partition.
/linux-6.12.1/arch/arm/lib/
Dclear_user.S43 it ne @ explicit IT needed for the label
/linux-6.12.1/scripts/coccinelle/api/
Dvma_pages.cocci3 /// Use vma_pages function on vma object instead of explicit computation.
Dresource_size.cocci4 /// instead of explicit computation.
/linux-6.12.1/Documentation/filesystems/
Dzonefs.rst311 * explicit-open
336 "explicit-open" option
341 implicit open, explicit open or closed conditions. This potential limitation
346 To avoid these potential errors, the "explicit-open" mount option forces zones
350 "explicit-open" mount option will result in a zone close command being issued
368 state of other zones. When the *explicit-open* mount option is used, zonefs
373 zone files open for writing. When the "explicit-open" mount option is used,
374 this number can never exceed *max_wro_seq_files*. If the *explicit-open*
382 is explicitly open (which happens only if the *explicit-open* mount option is
389 *nr_active_seq_files*, regardless of the use of the *explicit-open* mount
/linux-6.12.1/Documentation/block/
Dwriteback_cache_control.rst28 set on an otherwise empty bio structure, which causes only an explicit cache
45 worry if the underlying devices need any explicit cache flushing and how
/linux-6.12.1/scripts/coccinelle/misc/
Dboolconv.cocci5 //# explicit conversion is overly verbose and unneeded.
/linux-6.12.1/Documentation/devicetree/bindings/power/reset/
Dltc2952-poweroff.txt19 until an explicit kill signal is received
/linux-6.12.1/Documentation/ABI/obsolete/
Dsysfs-gpio8 userspace. GPIOs are only made available to userspace by an explicit
/linux-6.12.1/Documentation/userspace-api/media/dvb/
Dfe-get-property.rst54 parameters used. If the actual parameters are needed, an explicit
/linux-6.12.1/scripts/atomic/
Dgen-atomic-instrumented.sh138 * This file provoides atomic operations with explicit instrumentation (e.g.
/linux-6.12.1/virt/kvm/
DKconfig23 # put any explicit constraint on userspace ordering. They can also
/linux-6.12.1/scripts/coccinelle/iterators/
Ddevice_node_continue.cocci3 /// explicit put causes a double put.
/linux-6.12.1/drivers/gpu/drm/lima/
Dlima_gem.c263 bool write, bool explicit) in lima_gem_sync_bo() argument
272 if (explicit) in lima_gem_sync_bo()
/linux-6.12.1/Documentation/arch/arm/
Dcluster-pm-race-avoidance.rst153 a) an explicit hardware power-up operation, resulting
189 The CPU remains in this state until an explicit policy decision
197 explicit policy decision
309 a) an explicit hardware power-up operation, resulting
398 a) an explicit hardware power-up operation,

123456789