Home
last modified time | relevance | path

Searched refs:proceed (Results 1 – 25 of 86) sorted by relevance

1234

/linux/sound/soc/intel/avs/
H A Dtrace.h129 TP_PROTO(const char *op, bool proceed, u64 header),
131 TP_ARGS(op, proceed, header),
135 __field(bool, proceed )
141 __entry->proceed = proceed;
146 __entry->proceed ? "" : "ignore ", __get_str(op),
/linux/net/sched/
H A Dematch.c507 proceed: in __tcf_em_tree_match()
517 goto proceed; in __tcf_em_tree_match()
540 goto proceed; in __tcf_em_tree_match()
/linux/arch/x86/kernel/cpu/microcode/
H A Dcore.c497 bool proceed = true; in load_primary() local
501 proceed = kick_offline_cpus(nr_offl); in load_primary()
504 if (proceed) in load_primary()
/linux/tools/testing/selftests/powerpc/math/
H A Dvsx_asm.S26 # that the VMX have been loaded with varray. Will proceed to check the
H A Dvmx_asm.S114 # the VMX have been loaded with varray. Will proceed to check the validity of
H A Dfpu_asm.S133 # has been loaded with darray. Will proceed to check the validity of the FPU
/linux/Documentation/scsi/
H A Dscsi-parameters.rst98 allowing boot to proceed. none ignores them, expecting
/linux/drivers/perf/
H A Dxgene_pmu.c347 XGENE_PMU_EVENT_ATTR(mcu-rd-proceed-all, 0x16),
348 XGENE_PMU_EVENT_ATTR(mcu-rd-proceed-cancel, 0x17),
350 XGENE_PMU_EVENT_ATTR(mcu-rd-proceed-speculative-all, 0x19),
351 XGENE_PMU_EVENT_ATTR(mcu-rd-proceed-speculative-cancel, 0x1a),
352 XGENE_PMU_EVENT_ATTR(mcu-wr-proceed-all, 0x1b),
353 XGENE_PMU_EVENT_ATTR(mcu-wr-proceed-cancel, 0x1c),
/linux/Documentation/gpu/nova/core/
H A Ddevinit.rst46 Before the driver can proceed with further initialization, it must wait for a signal
/linux/Documentation/watchdog/
H A Dhpwdt.rst71 the iLO will proceed to reset the system at timeout if the timer hasn't
/linux/Documentation/ABI/testing/
H A Dsysfs-class-remoteproc83 copy the dump. Also recovery process will not proceed until
/linux/Documentation/networking/diagnostic/
H A Dtwisted_pair_layer1_diagnostics.rst90 proceed to the **Inspect Link Status and PHY Configuration** section.
105 proceed to the **Inspect Link Status and PHY Configuration** section to
120 transferred**, the issue is likely beyond Layer 1, and you should proceed
128 or power delivery problems. In this case, proceed with the next step in
289 on the system, proceed to the next diagnostic step, as power delivery is
320 established, proceed with further diagnostics by performing **Cable
/linux/Documentation/userspace-api/media/v4l/
H A Dv4l2grab.c.rst83 printf("Libv4l didn't accept RGB24 format. Can't proceed.\n");
/linux/drivers/net/wireless/broadcom/brcm80211/brcmfmac/
H A Dfirmware.c95 goto proceed; in brcmf_nvram_handle_idle()
104 proceed: in brcmf_nvram_handle_idle()
/linux/Documentation/admin-guide/device-mapper/
H A Dvdo-design.rst381 zone to proceed. The details of allocation are the same as in
389 waiting on this allocation also proceed.
406 it will proceed to search the next physical zone by taking the implicit
473 physical block as their new physical address and proceed to step 9
484 are out of space, so they proceed to step 13 for cleanup.
507 data_vio will proceed to step 8h to write its data directly.
526 possible. Each data_vio will then proceed to step 9 to record its
/linux/Documentation/process/
H A D3.Early-stage.rst188 idea. The best thing to do in this situation is to proceed, keeping the
212 experienced kernel developers may choose to proceed in an open-loop manner
/linux/Documentation/arch/powerpc/
H A Dsyscall64-abi.rst105 transactional state and the syscall will proceed as in the case of a
/linux/Documentation/bpf/
H A Dprog_cgroup_sysctl.rst53 * ``1`` means "proceed with access".
/linux/drivers/gpu/drm/i915/
H A DKconfig.profile131 concurrent execution in order for them to proceed, e.g. they
/linux/drivers/block/drbd/
H A Ddrbd_actlog.c1072 goto proceed; in drbd_try_rs_begin_io()
1117 proceed: in drbd_try_rs_begin_io()
/linux/Documentation/networking/
H A Dxdp-rx-metadata.rst153 case, the BPF program should not proceed to populate data into the ``data_meta``
/linux/Documentation/PCI/
H A Dpci-error-recovery.rst247 allowed to proceed, as another driver on the
254 reset to proceed.
410 - There is no guarantee that interrupt delivery can proceed from any
/linux/Documentation/driver-api/media/
H A Dcamera-sensor.rst120 runtime PM was disabled, in either of which cases the driver may proceed to
/linux/tools/perf/
H A Dbuiltin-sched.c1636 int proceed; in map_switch_event() local
1719 proceed = 0; in map_switch_event()
1734 proceed = 1; in map_switch_event()
1757 if (proceed != 1) { in map_switch_event()
1768 if (proceed == 1) in map_switch_event()
/linux/tools/lib/bpf/
H A Dusdt.c476 goto proceed; in parse_vma_segs()
484 proceed: in parse_vma_segs()

1234