| /openbmc/linux/Documentation/process/ |
| H A D | management-style.rst | 62 can be made small by just always making sure that if you were wrong (and
70 Thus the key to avoiding big decisions becomes to just avoiding to do
73 is just pitiful.
80 back-tracking is very easy: just tell everybody that you were an
94 too, and while the actual **work** was easy enough to undo by just
100 Happily, both of these reasons can be mitigated effectively by just
108 Then, when it really does turn out to be stupid, people just roll their
123 Btw, another way to avoid a decision is to plaintively just whine "can't
124 we just do both?" and look pitiful. Trust me, it works. If it's not
127 situation that they just give up.
[all …]
|
| /openbmc/linux/scripts/ |
| H A D | extract-module-sig.pl | 11 # -d: Just the descriptor values as a sequence of numbers
12 # -n: Just the signer's name
13 # -k: Just the key ID
14 # -s: Just the crypto signature or PKCS#7 message
120 # Just the descriptor values as a sequence of numbers
123 # Just the signer's name
129 # Just the key identifier
135 # Just the crypto signature or PKCS#7 message
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/graniterapids/ |
| H A D | memory.json | 10 …mpletion is greater than 128 cycles. Reported latency may be longer than just the memory latency.…
22 …ompletion is greater than 16 cycles. Reported latency may be longer than just the memory latency.…
34 …mpletion is greater than 256 cycles. Reported latency may be longer than just the memory latency.…
46 …ompletion is greater than 32 cycles. Reported latency may be longer than just the memory latency.…
58 …completion is greater than 4 cycles. Reported latency may be longer than just the memory latency.…
70 …mpletion is greater than 512 cycles. Reported latency may be longer than just the memory latency.…
82 …ompletion is greater than 64 cycles. Reported latency may be longer than just the memory latency.…
94 …completion is greater than 8 cycles. Reported latency may be longer than just the memory latency.…
|
| /openbmc/linux/Documentation/mm/ |
| H A D | active_mm.rst | 25 > discussed on the mailing lists---I just returned from vacation and
33 anonymous address space we just leave the previous address space
74 more. "init_mm" should be considered just a "lazy context when no other
75 context is available", and in fact it is mainly used just at bootup when
80 should generally just do
88 Anyway, I put a pre-patch-2.3.13-1 on ftp.kernel.org just a moment ago,
|
| /openbmc/linux/Documentation/userspace-api/media/rc/ |
| H A D | lirc-get-features.rst | 45 Unused. Kept just to avoid breaking uAPI.
51 Unused. Kept just to avoid breaking uAPI.
68 Unused. Kept just to avoid breaking uAPI.
144 Unused. Kept just to avoid breaking uAPI.
160 Unused. Kept just to avoid breaking uAPI.
167 Unused. Kept just to avoid breaking uAPI.
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | development-shell.rst | 6 When debugging certain commands or even when just editing packages,
14 ``configure`` and ``make``. The commands execute just as if the
57 the task just as it would be run using the ``bitbake -c`` command.
64 must be called just as BitBake would call them. That means you need to
75 instead of just using ``gcc``. The same applies to other
|
| /openbmc/linux/lib/kunit/ |
| H A D | executor_test.c | 20 /* .run_case is not important, just needs to be non-NULL */
61 /* Validate we just have suite2 */ in filter_suites_test()
81 /* Want: suite1, suite2, NULL -> suite2 (just test1), NULL */ in filter_suites_test_glob_test()
87 /* Validate we just have suite2 */ in filter_suites_test_glob_test()
92 /* Now validate we just have test2 */ in filter_suites_test_glob_test()
112 free_suite_set_at_end(test, &got); /* just in case */ in filter_suites_to_empty_test()
143 /* .run_case is not important, just needs to be non-NULL */
177 /* Validate we just have normal_suite */ in filter_attr_test()
182 /* Now validate we just have normal test case */ in filter_attr_test()
203 free_suite_set_at_end(test, &got); /* just in case */ in filter_attr_empty_test()
|
| /openbmc/phosphor-led-manager/test/ |
| H A D | utest.cpp | 37 // Need just the ledsAssserted populated with these. in TEST_F()
69 // Need just the ledsAssserted populated with these. in TEST_F()
101 // Need just the ledsAssserted populated with these. in TEST_F()
147 // Need just the ledsAssserted populated with these. in TEST_F()
183 // Need just the ledsAssserted populated with these. in TEST_F()
219 // Need just the ledsAssserted populated with these. in TEST_F()
249 // Need just the ledsAssserted populated with these. in TEST_F()
285 // Need just the ledsAssserted populated with these. in TEST_F()
315 // Need just the ledsAssserted populated with these. in TEST_F()
364 // Need just the ledsAssserted populated with these. in TEST_F()
[all …]
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | cputopology.rst | 46 7) topology_sibling_cpumask: just the given CPU
47 8) topology_core_cpumask: just the given CPU
48 9) topology_cluster_cpumask: just the given CPU
49 10) topology_die_cpumask: just the given CPU
50 11) topology_book_cpumask: just the given CPU
51 12) topology_drawer_cpumask: just the given CPU
|
| /openbmc/linux/kernel/module/ |
| H A D | dups.c | 81 * module is loaded so will just return 0 right away. There is still in kmod_dup_request_delete()
88 * just returning 0. in kmod_dup_request_delete()
114 * let this linger forever as this is just a boot optimization for in kmod_dup_request_complete()
147 * so just skip using them as an anchor. in kmod_dup_request_exists_wait()
161 * There was no duplicate, just add the request so we can in kmod_dup_request_exists_wait()
177 * You could also just queue a single request to load the module once, in kmod_dup_request_exists_wait()
191 * If request_module_nowait() was used then the user just in kmod_dup_request_exists_wait()
240 * and let duplicates suffer, just wait a tad bit longer. in kmod_dup_request_announce()
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/tigerlake/ |
| H A D | memory.json | 26 …mpletion is greater than 128 cycles. Reported latency may be longer than just the memory latency.…
38 …ompletion is greater than 16 cycles. Reported latency may be longer than just the memory latency.…
50 …mpletion is greater than 256 cycles. Reported latency may be longer than just the memory latency.…
62 …ompletion is greater than 32 cycles. Reported latency may be longer than just the memory latency.…
74 …completion is greater than 4 cycles. Reported latency may be longer than just the memory latency.…
86 …mpletion is greater than 512 cycles. Reported latency may be longer than just the memory latency.…
98 …ompletion is greater than 64 cycles. Reported latency may be longer than just the memory latency.…
110 …completion is greater than 8 cycles. Reported latency may be longer than just the memory latency.…
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/meteorlake/ |
| H A D | memory.json | 131 …pletion is greater than 1024 cycles. Reported latency may be longer than just the memory latency.…
144 …mpletion is greater than 128 cycles. Reported latency may be longer than just the memory latency.…
157 …ompletion is greater than 16 cycles. Reported latency may be longer than just the memory latency.…
170 …pletion is greater than 2048 cycles. Reported latency may be longer than just the memory latency.…
183 …mpletion is greater than 256 cycles. Reported latency may be longer than just the memory latency.…
196 …ompletion is greater than 32 cycles. Reported latency may be longer than just the memory latency.…
209 …completion is greater than 4 cycles. Reported latency may be longer than just the memory latency.…
222 …mpletion is greater than 512 cycles. Reported latency may be longer than just the memory latency.…
235 …ompletion is greater than 64 cycles. Reported latency may be longer than just the memory latency.…
248 …completion is greater than 8 cycles. Reported latency may be longer than just the memory latency.…
|
| /openbmc/linux/tools/testing/selftests/bpf/prog_tests/ |
| H A D | atomics.c | 12 /* No need to attach it, just run it directly */ in test_add()
37 /* No need to attach it, just run it directly */ in test_sub()
62 /* No need to attach it, just run it directly */ in test_and()
84 /* No need to attach it, just run it directly */ in test_or()
106 /* No need to attach it, just run it directly */ in test_xor()
128 /* No need to attach it, just run it directly */ in test_cmpxchg()
150 /* No need to attach it, just run it directly */ in test_xchg()
|
| /openbmc/qemu/scripts/oss-fuzz/ |
| H A D | reorder_fuzzer_qtest_trace.py | 21 Some fuzzer make use of hooks that allow us to populate some memory range, just
27 [start] fill a DMA buffer just in time
28 [end] fill a DMA buffer just in time
29 [start] fill a DMA buffer just in time
30 [end] fill a DMA buffer just in time
|
| /openbmc/linux/Documentation/scheduler/ |
| H A D | sched-stats.rst | 111 cpu was just becoming idle
113 load did not require balancing when the cpu was just becoming idle
115 tasks and failed, when the cpu was just becoming idle
117 load_balance() in this domain when the cpu was just becoming idle
120 target task was cache-hot when just becoming idle
122 find a busier queue while the cpu was just becoming idle
124 was just becoming idle but no busier group was found
|
| /openbmc/linux/scripts/coccinelle/misc/ |
| H A D | warn.cocci | 35 cocci.print_main("printk + WARN_ON can be just WARN",p)
41 msg = "SUGGESTION: printk + WARN_ON can be just WARN"
84 cocci.print_main("printk + WARN_ON_ONCE can be just WARN_ONCE",p)
90 msg = "SUGGESTION: printk + WARN_ON_ONCE can be just WARN_ONCE"
|
| /openbmc/linux/Documentation/maintainer/ |
| H A D | pull-requests.rst | 28 have just created. It is recommended that you choose a meaningful tag name,
60 not just make sense to me, but make sense as a historical record
66 diffstat anyway, and if you didn't mention it, I'll just be extra
68 (or even bug-fixes, but ones that look scary), explain not just
76 tag just a placeholder with nothing interesting in it, and describe
79 And yes, I will edit the message. Partly because I tend to do just
121 The tag message format is just like a git commit id. One line at the top
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/alderlake/ |
| H A D | memory.json | 123 …mpletion is greater than 128 cycles. Reported latency may be longer than just the memory latency.…
136 …ompletion is greater than 16 cycles. Reported latency may be longer than just the memory latency.…
149 …mpletion is greater than 256 cycles. Reported latency may be longer than just the memory latency.…
162 …ompletion is greater than 32 cycles. Reported latency may be longer than just the memory latency.…
175 …completion is greater than 4 cycles. Reported latency may be longer than just the memory latency.…
188 …mpletion is greater than 512 cycles. Reported latency may be longer than just the memory latency.…
201 …ompletion is greater than 64 cycles. Reported latency may be longer than just the memory latency.…
214 …completion is greater than 8 cycles. Reported latency may be longer than just the memory latency.…
|
| /openbmc/linux/arch/xtensa/lib/ |
| H A D | strnlen_user.S | 101 # NOTE that in several places below, we point to the byte just after
107 addi a4, a4, 1 # point just beyond zero byte
111 addi a4, a4, 1+1 # point just beyond zero byte
115 addi a4, a4, 2+1 # point just beyond zero byte
131 addi a4, a4, 3+1 # point just beyond zero byte
|
| /openbmc/openpower-proc-control/procedures/phal/ |
| H A D | check_host_running.cpp | 46 // just continue, failing to collect a dump should not cause further in createBmcDump()
72 // This should "never" happen so just throw the exception and let in checkHostRunning()
99 // On error, we have to assume host is up so just fall through in checkHostRunning()
153 // This should "never" happen so just throw the exception and let in clearHostRunning()
176 // It's best effort, so just return either way in clearHostRunning()
|
| /openbmc/linux/fs/pstore/ |
| H A D | Kconfig | 10 provide the data, so you probably should just go say "Y"
139 This just sets size of kmsg dump (oops, panic, etc) log for
163 This just sets size of pmsg (pmsg_size) for pstore/blk. The size is
175 This just sets size of console log (console_size) to store via
187 This just sets size of ftrace log (ftrace_size) for pstore/blk. The
|
| /openbmc/linux/tools/testing/ktest/examples/include/ |
| H A D | patchcheck.conf | 41 # run some test scripts. If you just want to boot test your patches
56 # Instead of just checking for warnings to files that are changed
85 # Note, do not change this option. Just define PATCH_START1 in the
87 # otherwise it will just use PATCH_START if PATCH_START1 is not defined.
|
| /openbmc/linux/drivers/gpu/drm/msm/ |
| H A D | NOTES | 30 (Second part is not implemented yet. So far this is just basic KMS
58 register interface is same, just different bases.)
67 Each connector probably ends up being a separate device, just for the
69 have a better way than just stashing the platform device in a global
|
| /openbmc/linux/Documentation/dev-tools/ |
| H A D | sparse.rst | 35 ends up looking just like integers to gcc.
37 Quite frankly, you don't need the enum there. The above all really just
40 So the simpler way is to just do::
86 Once you have it, just do::
|
| /openbmc/openbmc/meta-yadro/recipes-phosphor/ipmi/phosphor-ipmi-host/ |
| H A D | 0001-Add-support-for-persistent-only-settings.patch | 48 + // On the contrary, if there is just one object, that may mean
51 + // That is not an error, just return the regular setting.
52 + // If there's just one object, that's the only kind of setting
53 + // mode this interface supports, so just return that setting path.
|