Searched refs:after (Results 1 – 25 of 115) sorted by relevance
12345
11 after: [ ! -f d1/d2/x.txt ]23 after: [ ! -f d1/d2/x.txt ]34 after: [ ! -f d1/d2/file ]46 after: [ ! -f d1/d2/file ]58 after: [ ! -f d1/d2/b.txt ]65 after: [ -f d1/d2/a.txt ]66 after: [ -f d1/d2/b.txt ]67 after: [ -f d1/d2/c.txt ]68 after: [ -f d1/d2/empty.txt ]69 after: [ -f d1/d2/x.txt ][all …]
353 static struct cpu_disk_util_stats after; variable518 read_disk_util_state(&after); in report_cpu_disk_util()519 read_cpu_util_state(&after); in report_cpu_disk_util()521 tot2 = after.user_cpu_ticks + after.nice_cpu_ticks + in report_cpu_disk_util()522 after.system_cpu_ticks + after.hardirq_cpu_ticks + in report_cpu_disk_util()523 after.softirq_cpu_ticks; in report_cpu_disk_util()528 tot2 += after.iowait_cpu_ticks + after.idle_cpu_ticks; in report_cpu_disk_util()537 delta1 = (after.user_cpu_ticks + after.nice_cpu_ticks) - in report_cpu_disk_util()544 delta1 = (after.system_cpu_ticks + after.hardirq_cpu_ticks + in report_cpu_disk_util()545 after.softirq_cpu_ticks) - in report_cpu_disk_util()[all …]
32 stop_event: <logcat log message which will terminate log collection after reboot>37 On some devise clock is showing incorrect time for first couple of seconds after boot.39 be present in dmesg log after clock correction.
39 after: [ ! -f d1/d2/x.txt ]54 more `after:` lines (run after `command:`). These are useful for both57 Any `command:`, `before:`, or `after:` line is expected to exit with status 0.80 this. In the meantime, it's possible to use an `after:` with `grep -q` if
36 buffer_type from the buffers specified by `buffers` starting after the number of logs specified by37 `print_point` have been logged. This acts as if a user called `logcat` immediately after the38 specified logs have been logged. It additionally prints the statistics from `logcat -S` after the42 `print_point` is an positive integer. If it is unspecified, logs are printed after the entire
4 /* these name could be suffix compressed in dtb after compiled */
48 // equivalent. e.g. "America/Boise" has the same rules as "America/Denver" after Sun, 03 Feb61 // The functional replacement of one time zone ID by another after a point in time.66 // The Olson ID that is better / to use in place of replacedId on Android after fromMillis.
16 # reinitialize lmkd after device finished booting if experiments set any flags during boot22 # if the device finished booting or sets lmkd.reinit=0 to re-initialize lmkd after boot completes
62 - `ro.lmk.kill_timeout_ms`: duration in ms after a kill when no additional81 after a kill. Default for low-RAM devices = 50,92 cycle after kill used to allow blocking of killing
47 All characters after the symbol size and until the end of the line are parsed as the symbol name,53 a file either before or after.
35 [ label = "'name \"disassembly (after)\"'" ];37 [ label = "NOT('name \"disassembly (after)\"')" ];
2 # after performing an adb root command.
31 description: "Abandon Keystore database retry loop after an interval"
2 // Do not modify this file after the first "rust_*" or "genrule" module
7 # TODO(b/112338294): remove these after migrate to Binder
21 TWO = 1 /* definitely unrecognized comment (after enumerator) */
24 * @param multiple is the correct param, just after the @return
12 # root.root to system.log, may be deleted after ota has settled.63 # Need go after persist peroperties are loaded which is right before zygote-start trigger
91 // Ignore memory leaks after ASSERT_NE in DisableMalloc_test.cpp.
28 And then attempt to exactly match the token after `:`, `0000000000003000`,
24 // data has been received, after a previously received ENABLE_AUDIO
25 #### after subsubsection62 #### after subsubsection
61 to be written for that - modeled after the disk_stats_before/after
24 directories will not be parsed. Imported files are parsed after the current file has been parsed.108 `/apex/*/etc/firmware` is also searched after a list of firmware directories.121 Ueventd will wait until after `post-fs` in init, to keep retrying before believing the firmwares are149 console after the external program has exited.