Searched refs:continuing (Results 1 – 25 of 26) sorted by relevance
12
| /Linux-v5.4/Documentation/admin-guide/LSM/ |
| D | SELinux.rst | 23 before continuing.
|
| /Linux-v5.4/Documentation/media/dvb-drivers/ |
| D | contributors.rst | 24 - for their continuing work on the DVB driver
|
| /Linux-v5.4/Documentation/powerpc/ |
| D | syscall64-abi.rst | 51 continuing at the instruction following the sc instruction.
|
| /Linux-v5.4/arch/m68k/fpsp040/ |
| D | x_store.S | 142 | ; before continuing
|
| /Linux-v5.4/Documentation/trace/ |
| D | tracepoints.rst | 25 provided ends its execution, it returns to the caller (continuing from
|
| D | ring-buffer-design.txt | 218 transaction. If another write happens it must finish before continuing
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | device-io.rst | 87 continuing execution::
|
| /Linux-v5.4/Documentation/networking/ |
| D | fib_trie.txt | 136 At this point we backtrack (t->stats.backtrack++) up the trie, continuing to
|
| D | can.rst | 851 'ival1', then continuing to send at another given interval 'ival2'. When
|
| D | filter.txt | 424 will walk through the pcap file continuing from the current packet and
|
| /Linux-v5.4/drivers/usb/dwc2/ |
| D | gadget.c | 1016 bool continuing) in dwc2_hsotg_start_req() argument
1031 if (hs_ep->req && !continuing) { in dwc2_hsotg_start_req()
1035 } else if (hs_ep->req != hs_req && continuing) { in dwc2_hsotg_start_req()
1103 if (dir_in && ureq->zero && !continuing) { in dwc2_hsotg_start_req()
1137 continuing) in dwc2_hsotg_start_req()
1153 if (using_dma(hsotg) && !continuing && (length != 0)) { in dwc2_hsotg_start_req()
|
| /Linux-v5.4/Documentation/crypto/ |
| D | devel-algos.rst | 54 transformations, continuing on error. It logs errors and always
|
| /Linux-v5.4/Documentation/process/ |
| D | code-of-conduct-interpretation.rst | 105 The Code of Conduct does not prohibit continuing to include names, email
|
| /Linux-v5.4/Documentation/x86/ |
| D | intel_txt.rst | 135 or simply logging them and continuing.
|
| /Linux-v5.4/Documentation/scsi/ |
| D | aic7xxx.txt | 172 problem, continuing to report the errors just degrades
|
| /Linux-v5.4/Documentation/locking/ |
| D | lockdep-design.rst | 26 continuing effort to prove lock usages and dependencies are correct or
|
| /Linux-v5.4/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.
|
| D | aic79xx.seq | 1438 * before continuing.
|
| /Linux-v5.4/scripts/ |
| D | spelling.txt | 353 continueing||continuing
|
| /Linux-v5.4/Documentation/usb/ |
| D | usb-serial.rst | 143 reset button, continuing to hold onto the power until the bootloader screen
|
| /Linux-v5.4/Documentation/ |
| D | DMA-API.txt | 578 continuing on for size. Again, you *must* observe the cache line
|
| /Linux-v5.4/Documentation/admin-guide/sysctl/ |
| D | kernel.rst | 609 Rather than continuing, panicking might be a better choice. Some
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | dev-decoder.rst | 1006 such as the `Dynamic Resolution Change` sequence, before continuing with
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | ras.rst | 778 system context might be so mangled that continuing will lead to further
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | path-lookup.rst | 228 it might end up continuing the search down the wrong chain,
|
12
