| /kernel/linux/linux-4.19/Documentation/media/uapi/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.
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/Documentation/process/ |
| D | management-style.rst | 61 can be made small by just always making sure that if you were wrong (and
69 Thus the key to avoiding big decisions becomes to just avoiding to do
72 is just pitiful.
79 back-tracking is very easy: just tell everybody that you were an
93 too, and while the actual **work** was easy enough to undo by just
99 Happily, both of these reasons can be mitigated effectively by just
107 Then, when it really does turn out to be stupid, people just roll their
122 Btw, another way to avoid a decision is to plaintively just whine "can't
123 we just do both?" and look pitiful. Trust me, it works. If it's not
126 situation that they just give up.
[all …]
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-5.10/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,
|
| /kernel/linux/linux-4.19/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,
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | tracehook.h | 26 * need to understand all the calling core or arch code in detail, just
87 * current task has just entered the kernel for a system call.
99 * Called without locks, just after entering kernel mode.
108 * tracehook_report_syscall_exit - task has just finished a system call
113 * current task has just finished an attempted system call. Full
122 * Called without locks, just before checking for pending signals.
187 * The caller just cleared TIF_NOTIFY_RESUME. This barrier in tracehook_notify_resume()
|
| /kernel/linux/linux-4.19/Documentation/scheduler/ |
| D | sched-stats.txt | 104 cpu was just becoming idle
106 load did not require balancing when the cpu was just becoming idle
108 tasks and failed, when the cpu was just becoming idle
110 load_balance() in this domain when the cpu was just becoming idle
113 target task was cache-hot when just becoming idle
115 find a busier queue while the cpu was just becoming idle
117 was just becoming idle but no busier group was found
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/scripts/coccinelle/misc/ |
| D | warn.cocci | 34 cocci.print_main("printk + WARN_ON can be just WARN",p)
40 msg = "SUGGESTION: printk + WARN_ON can be just WARN"
83 cocci.print_main("printk + WARN_ON_ONCE can be just WARN_ONCE",p)
89 msg = "SUGGESTION: printk + WARN_ON_ONCE can be just WARN_ONCE"
|
| /kernel/linux/linux-5.10/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"
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/fs/pstore/ |
| D | Kconfig | 11 provide the data, so you probably should just go say "Y"
225 This just sets size of kmsg dump (oops, panic, etc) log for
249 This just sets size of pmsg (pmsg_size) for pstore/blk. The size is
261 This just sets size of console log (console_size) to store via
273 This just sets size of ftrace log (ftrace_size) for pstore/blk. The
285 This just sets size of fault log (blackbox_size) for pstore/blk.
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | tracehook.h | 23 * need to understand all the calling core or arch code in detail, just
87 * when the current task has just entered the kernel for a system call.
99 * Called without locks, just after entering kernel mode.
108 * tracehook_report_syscall_exit - task has just finished a system call
113 * current task has just finished an attempted system call. Full
122 * Called without locks, just before checking for pending signals.
|
| /kernel/linux/linux-5.10/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?
|
| /kernel/linux/linux-4.19/Documentation/ |
| D | bus-virt-phys-mapping.txt | 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?
|
| /kernel/linux/linux-4.19/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.
|
| /kernel/linux/linux-5.10/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::
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-5.10/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
|