Searched refs:continuing (Results 1 – 25 of 33) sorted by relevance
12
| /linux-6.12.1/crypto/ |
| D | algif_hash.c | 71 bool continuing, need_init = false; in hash_sendmsg() local
78 continuing = ctx->more; in hash_sendmsg()
80 if (!continuing) { in hash_sendmsg()
135 if (!msg_data_left(msg) && !continuing && in hash_sendmsg()
152 continuing = true; in hash_sendmsg()
|
| /linux-6.12.1/Documentation/admin-guide/LSM/ |
| D | SELinux.rst | 23 before continuing.
|
| /linux-6.12.1/Documentation/driver-api/media/drivers/ |
| D | contributors.rst | 24 - for their continuing work on the DVB driver
|
| /linux-6.12.1/arch/m68k/fpsp040/ |
| D | x_store.S | 142 | ; before continuing
|
| /linux-6.12.1/Documentation/arch/powerpc/ |
| D | syscall64-abi.rst | 11 continuing at the instruction following the sc instruction.
|
| /linux-6.12.1/Documentation/trace/ |
| D | tracepoints.rst | 25 provided ends its execution, it returns to the caller (continuing from
|
| D | ring-buffer-design.rst | 242 transaction. If another write happens it must finish before continuing
|
| D | events.rst | 867 by the subsequent call, continuing until all the fields have been set
|
| /linux-6.12.1/Documentation/networking/ |
| D | fib_trie.rst | 140 At this point we backtrack (t->stats.backtrack++) up the trie, continuing to
|
| D | filter.rst | 467 will walk through the pcap file continuing from the current packet and
|
| /linux-6.12.1/Documentation/process/ |
| D | cve.rst | 11 combination of continuing pressure to assign CVEs and other forms of
|
| D | code-of-conduct-interpretation.rst | 105 The Code of Conduct does not prohibit continuing to include names, email
|
| /linux-6.12.1/drivers/usb/dwc2/ |
| D | gadget.c | 1051 bool continuing) in dwc2_hsotg_start_req() argument
1066 if (hs_ep->req && !continuing) { in dwc2_hsotg_start_req()
1070 } else if (hs_ep->req != hs_req && continuing) { in dwc2_hsotg_start_req()
1133 if (dir_in && ureq->zero && !continuing) { in dwc2_hsotg_start_req()
1161 if (continuing) in dwc2_hsotg_start_req()
1177 if (using_dma(hsotg) && !continuing && (length != 0)) { in dwc2_hsotg_start_req()
|
| /linux-6.12.1/Documentation/arch/x86/ |
| D | intel_txt.rst | 135 or simply logging them and continuing.
|
| /linux-6.12.1/Documentation/virt/kvm/ |
| D | vcpu-requests.rst | 132 sender of the request continuing on. No action needs be taken by the target,
|
| /linux-6.12.1/Documentation/scsi/ |
| D | aic7xxx.rst | 183 problem, continuing to report the errors just degrades
|
| /linux-6.12.1/drivers/scsi/aic7xxx/ |
| D | aic7xxx.seq | 1982 * before continuing.
1999 * from out to in, wait an additional data release delay before continuing.
2113 * before continuing.
|
| /linux-6.12.1/Documentation/usb/ |
| D | usb-serial.rst | 143 reset button, continuing to hold onto the power until the bootloader screen
|
| /linux-6.12.1/scripts/ |
| D | spelling.txt | 415 continueing||continuing
|
| /linux-6.12.1/Documentation/driver-api/ |
| D | device-io.rst | 87 continuing execution::
|
| /linux-6.12.1/Documentation/bpf/ |
| D | kfuncs.rst | 425 subsystem in question, and of course what the technical cost is of continuing
|
| /linux-6.12.1/Documentation/locking/ |
| D | lockdep-design.rst | 26 continuing effort to prove lock usages and dependencies are correct or
|
| /linux-6.12.1/Documentation/driver-api/surface_aggregator/ |
| D | internal.rst | 94 before continuing with the architectural overview below.
|
| /linux-6.12.1/Documentation/admin-guide/device-mapper/ |
| D | vdo-design.rst | 501 evict waiting data_vios when continuing to wait would cause
|
| /linux-6.12.1/Documentation/admin-guide/RAS/ |
| D | main.rst | 791 system context might be so mangled that continuing will lead to further
|
12