| /Linux-v5.15/Documentation/process/ |
| 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 …]
|
| /Linux-v5.15/Documentation/userspace-api/media/rc/ |
| 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.
109 Unused. Kept just to avoid breaking uAPI.
136 Unused. Kept just to avoid breaking uAPI.
156 Unused. Kept just to avoid breaking uAPI.
162 Unused. Kept just to avoid breaking uAPI.
178 Unused. Kept just to avoid breaking uAPI.
185 Unused. Kept just to avoid breaking uAPI.
|
| /Linux-v5.15/scripts/ |
| 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
|
| /Linux-v5.15/Documentation/vm/ |
| D | active_mm.rst | 21 > discussed on the mailing lists---I just returned from vacation and
29 anonymous address space we just leave the previous address space
70 more. "init_mm" should be considered just a "lazy context when no other
71 context is available", and in fact it is mainly used just at bootup when
76 should generally just do
84 Anyway, I put a pre-patch-2.3.13-1 on ftp.kernel.org just a moment ago,
|
| /Linux-v5.15/Documentation/scheduler/ |
| 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
|
| /Linux-v5.15/scripts/coccinelle/misc/ |
| 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"
|
| /Linux-v5.15/Documentation/maintainer/ |
| D | pull-requests.rst | 30 have just created. It is recommended that you choose a meaningful tag name,
62 not just make sense to me, but make sense as a historical record
68 diffstat anyway, and if you didn't mention it, I'll just be extra
70 (or even bug-fixes, but ones that look scary), explain not just
78 tag just a placeholder with nothing interesting in it, and describe
81 And yes, I will edit the message. Partly because I tend to do just
123 The tag message format is just like a git commit id. One line at the top
|
| /Linux-v5.15/arch/xtensa/lib/ |
| 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
|
| /Linux-v5.15/Documentation/core-api/ |
| D | bus-virt-phys-mapping.rst | 50 Now, just as an example, on the PReP (PowerPC Reference Platform), the
71 where all the addresses actually point to the same thing. It's just seen
130 address in some cases, it's just not very often in normal code. The physical
144 of a video graphics card it can be normal DRAM that is just used for a frame
152 just dereference a pointer. (Sadly, on x86 it **is** in the same memory space,
153 so on x86 it actually works to just deference a pointer, but it's not
191 OK, that just about covers the basics of accessing IO portably. Questions?
|
| /Linux-v5.15/tools/perf/pmu-events/arch/x86/icelakex/ |
| D | memory.json | 174 …completion is greater than 4 cycles. Reported latency may be longer than just the memory latency.…
190 …completion is greater than 8 cycles. Reported latency may be longer than just the memory latency.…
206 …ompletion is greater than 16 cycles. Reported latency may be longer than just the memory latency.…
222 …ompletion is greater than 32 cycles. Reported latency may be longer than just the memory latency.…
238 …ompletion is greater than 64 cycles. Reported latency may be longer than just the memory latency.…
254 …mpletion is greater than 128 cycles. Reported latency may be longer than just the memory latency.…
270 …mpletion is greater than 256 cycles. Reported latency may be longer than just the memory latency.…
286 …mpletion is greater than 512 cycles. Reported latency may be longer than just the memory latency.…
|
| /Linux-v5.15/tools/perf/pmu-events/arch/x86/tigerlake/ |
| D | memory.json | 35 …mpletion is greater than 128 cycles. Reported latency may be longer than just the memory latency.…
51 …ompletion is greater than 16 cycles. Reported latency may be longer than just the memory latency.…
67 …mpletion is greater than 256 cycles. Reported latency may be longer than just the memory latency.…
83 …ompletion is greater than 32 cycles. Reported latency may be longer than just the memory latency.…
99 …completion is greater than 4 cycles. Reported latency may be longer than just the memory latency.…
115 …mpletion is greater than 512 cycles. Reported latency may be longer than just the memory latency.…
131 …ompletion is greater than 64 cycles. Reported latency may be longer than just the memory latency.…
147 …completion is greater than 8 cycles. Reported latency may be longer than just the memory latency.…
|
| /Linux-v5.15/include/linux/ |
| D | tracehook.h | 23 * need to understand all the calling core or arch code in detail, just
87 * %SYSCALL_WORK_SYSCALL_EMU have been set, when the current task has just
100 * Called without locks, just after entering kernel mode.
109 * tracehook_report_syscall_exit - task has just finished a system call
114 * the current task has just finished an attempted system call. Full
123 * Called without locks, just before checking for pending signals.
|
| /Linux-v5.15/tools/testing/ktest/examples/include/ |
| 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.
|
| /Linux-v5.15/Documentation/dev-tools/ |
| 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::
|
| /Linux-v5.15/drivers/gpu/drm/msm/ |
| 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
|
| /Linux-v5.15/drivers/gpu/drm/i915/gem/ |
| D | i915_gem_pm.c | 69 * machines is a good idea, we don't - just in case it leaves the in i915_gem_suspend_late()
104 * Called just before we write the hibernation image. in i915_gem_freeze_late()
112 * we update that state just before writing out the image. in i915_gem_freeze_late()
135 * guarantee that the context image is complete. So let's just reset in i915_gem_resume()
|
| /Linux-v5.15/fs/pstore/ |
| D | Kconfig | 11 provide the data, so you probably should just go say "Y"
221 This just sets size of kmsg dump (oops, panic, etc) log for
245 This just sets size of pmsg (pmsg_size) for pstore/blk. The size is
257 This just sets size of console log (console_size) to store via
269 This just sets size of ftrace log (ftrace_size) for pstore/blk. The
|
| /Linux-v5.15/drivers/regulator/ |
| D | irq_helpers.c | 81 * just enable IRQ and bail-out. in regulator_notifier_isr_work()
101 * just in case the renable changed it. in regulator_notifier_isr_work()
177 * Maybe we should just to be on a safer side(?) in regulator_notifier_isr()
183 * IRQ but just increase fail count and retry when IRQ fires again. in regulator_notifier_isr()
187 * If no die handler is given we will just power-off as a last resort. in regulator_notifier_isr()
191 * if IC has no die-handler populated we just assume the regulator in regulator_notifier_isr()
264 /* If we have no recovery, just try shut down straight away */ in regulator_notifier_isr()
|
| /Linux-v5.15/tools/testing/ktest/ |
| D | sample.conf | 180 # a file is processed just like the contents of the file was cut and pasted
272 # just like you can config variables.
471 # just define all default options before the first TEST_START
560 # If for some reason you just want to boot the kernel and you do not
561 # want the test to install anything new. For example, you may just want
645 # after the install, where this one runs just before a reboot.
696 # Sometimes there's options that just break the boot and
800 # not want the test to fail just because the system was in
863 # Note, POWERCYCLE_AFTER_REBOOT = 0 does NOT disable it. It just
872 # Note, POWEROFF_AFTER_HALT = 0 does NOT disable it. It just
[all …]
|
| /Linux-v5.15/drivers/spi/ |
| D | spi-test.h | 89 #define FILL_MEMSET_8 0 /* just memset with 8 bit */
90 #define FILL_MEMSET_16 1 /* just memset with 16 bit */
91 #define FILL_MEMSET_24 2 /* just memset with 24 bit */
92 #define FILL_MEMSET_32 3 /* just memset with 32 bit */
|
| /Linux-v5.15/arch/x86/include/uapi/asm/ |
| D | stat.h | 31 /* We don't need to memset the whole thing just to initialize the padding */
75 /* We don't need to memset the whole thing just to initialize the padding */
106 /* We don't need to memset the whole thing just to initialize the padding */
|
| /Linux-v5.15/kernel/kcsan/ |
| D | permissive.h | 51 * A common pattern is checking/setting just 1 bit in a variable; for in kcsan_ignore_data_race()
58 * flags |= SOME_OTHER_FLAG; // just 1 bit in kcsan_ignore_data_race()
73 * Of course many operations can effecively change just 1 bit, but the in kcsan_ignore_data_race()
|
| /Linux-v5.15/arch/riscv/include/asm/ |
| D | barrier.h | 25 /* These barriers do not need to enforce ordering on devices, just memory. */
60 * on that one lock. Thus, we're just doing a full fence.
65 * any concrete reason we need a full IO fence, it seems safer to just upgrade
|
| /Linux-v5.15/Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-elog | 47 Currently just "0x00 PEL" - platform error log.
52 <16kb, often just hundreds of bytes and
61 operations (currently just acknowledge).
|
| /Linux-v5.15/drivers/gpu/drm/amd/display/ |
| D | TODO | 15 * dc_stream/core_stream/stream should just be dc_stream
90 incompatible styles, just means more reasons not to add a third (or well third
96 share it with drivers. But that's a very long term goal, and by far not just an
101 DRM_DEBUG stuff just isn't up to the challenges either. We need to figure out
|
