| /linux/net/sched/ |
| H A D | ematch.c | 507 proceed: in __tcf_em_tree_match()
517 goto proceed; in __tcf_em_tree_match()
540 goto proceed; in __tcf_em_tree_match()
|
| /linux/tools/testing/selftests/powerpc/math/ |
| H A D | vsx_asm.S | 26 # that the VMX have been loaded with varray. Will proceed to check the
|
| H A D | fpu_asm.S | 133 # has been loaded with darray. Will proceed to check the validity of the FPU
|
| H A D | vmx_asm.S | 114 # the VMX have been loaded with varray. Will proceed to check the validity of
|
| /linux/Documentation/scsi/ |
| H A D | scsi-parameters.rst | 98 allowing boot to proceed. none ignores them, expecting
|
| /linux/Documentation/gpu/nova/core/ |
| H A D | devinit.rst | 46 Before the driver can proceed with further initialization, it must wait for a signal
|
| /linux/Documentation/watchdog/ |
| H A D | hpwdt.rst | 71 the iLO will proceed to reset the system at timeout if the timer hasn't
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-remoteproc | 83 copy the dump. Also recovery process will not proceed until
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | v4l2grab.c.rst | 84 printf("Libv4l didn't accept RGB24 format. Can't proceed.\n");
|
| /linux/drivers/net/wireless/broadcom/brcm80211/brcmfmac/ |
| H A D | firmware.c | 95 goto proceed; in brcmf_nvram_handle_idle()
104 proceed: in brcmf_nvram_handle_idle()
|
| /linux/Documentation/process/ |
| H A D | 3.Early-stage.rst | 188 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/bpf/ |
| H A D | prog_cgroup_sysctl.rst | 53 * ``1`` means "proceed with access".
|
| /linux/drivers/gpu/drm/i915/ |
| H A D | Kconfig.profile | 131 concurrent execution in order for them to proceed, e.g. they
|
| /linux/Documentation/arch/powerpc/ |
| H A D | syscall64-abi.rst | 105 transactional state and the syscall will proceed as in the case of a
|
| /linux/drivers/block/drbd/ |
| H A D | drbd_actlog.c | 1072 goto proceed; in drbd_try_rs_begin_io()
1117 proceed: in drbd_try_rs_begin_io()
|
| /linux/Documentation/networking/ |
| H A D | xdp-rx-metadata.rst | 153 case, the BPF program should not proceed to populate data into the ``data_meta``
|
| H A D | strparser.rst | 137 can proceed to read the messages itself
|
| /linux/tools/memory-model/ |
| H A D | linux-kernel.cat | 125 * Effects of read-side critical sections proceed from the rcu_read_unlock()
|
| /linux/Documentation/core-api/ |
| H A D | assoc_array.rst | 83 proceed under the RCU read lock.
506 proceed rootwards through the tree, going to the parent node, slot N + 1 to
|
| /linux/Documentation/power/ |
| H A D | userland-swsusp.rst | 164 in the memory location pointed to by the last argument of ioctl() and proceed
|
| /linux/tools/perf/ |
| H A D | builtin-sched.c | 1643 int proceed; in map_switch_event() local
1726 proceed = 0; in map_switch_event()
1741 proceed = 1; in map_switch_event()
1764 if (proceed != 1) { in map_switch_event()
1775 if (proceed == 1) in map_switch_event()
|
| /linux/Documentation/staging/ |
| H A D | crc32.rst | 34 Just like with ordinary division, you proceed one digit (bit) at a time.
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | verity.rst | 79 Log corrupted blocks, but allow read operations to proceed normally.
|
| /linux/Documentation/scheduler/ |
| H A D | completion.rst | 15 yield() or some quirky msleep(1) loop to allow something else to proceed,
|
| /linux/tools/memory-model/Documentation/ |
| H A D | litmus-tests.txt | 316 below, P0() is one side checking to see if an operation may proceed and
555 Rather unconventionally, execution appears to proceed to the critical
603 executions in which both critical sections proceed concurrently. In
|