Searched full:obvious (Results 1 – 25 of 261) sorted by relevance
1234567891011
| /Linux-v5.10/Documentation/ia64/ |
| D | ia64.rst | 42 * Hardly any performance tuning has been done. Obvious targets
44 obvious targets include making sure we don't flush the TLB
|
| /Linux-v5.10/Documentation/process/ |
| D | management-style.rst | 27 making it painfully obvious to the questioner that we don't have a clue
39 manager must be to make it. That's very deep and obvious, but it's not
254 don't try to make it too obvious unless you really **intend** to irritate
279 peoples mistakes, and make it painfully obvious to everybody else that
280 you're incompetent, the obvious question becomes one of why do it in the
|
| /Linux-v5.10/drivers/staging/rtl8188eu/ |
| D | TODO | 2 - find and remove remaining code valid only for 5 GHz. Most of the obvious
|
| /Linux-v5.10/drivers/staging/rtl8723bs/ |
| D | TODO | 3 - find and remove remaining code valid only for 5 GHz. Most of the obvious
|
| /Linux-v5.10/arch/mips/sni/ |
| D | eisa.c | 16 * Now use a platform device, since that's the obvious choice. */
|
| /Linux-v5.10/drivers/eisa/ |
| D | virtual_root.c | 26 * Now use a platform device, since that's the obvious choice. */
|
| /Linux-v5.10/Documentation/sh/ |
| D | register-banks.rst | 21 in mind when writing code that utilizes these banked registers, for obvious
|
| /Linux-v5.10/Documentation/kbuild/ |
| D | Kconfig.recursion-issue-01 | 37 # obvious that an easy to solution to this problem should just be the removal
|
| D | Kconfig.recursion-issue-02 | 18 # A perhaps not so obvious implication of this is that, if semantics on these
|
| /Linux-v5.10/Documentation/maintainer/ |
| D | modifying-patches.rst | 16 name, all enclosed in square brackets, is noticeable enough to make it obvious
|
| /Linux-v5.10/Documentation/driver-api/gpio/ |
| D | using-gpio.rst | 6 as such are normally not user facing abstractions. The most obvious, natural
|
| /Linux-v5.10/Documentation/vm/ |
| D | overcommit-accounting.rst | 10 Heuristic overcommit handling. Obvious overcommits of address
|
| D | active_mm.rst | 32 The obvious use for a "anonymous address space" is any thread that
|
| /Linux-v5.10/Documentation/userspace-api/ |
| D | no_new_privs.rst | 6 its parent did not have. The most obvious examples are setuid/setgid
|
| /Linux-v5.10/arch/mips/include/asm/ |
| D | unroll.h | 23 * up until 8.0 tend to miss obvious constants & cause \
|
| /Linux-v5.10/Documentation/scsi/ |
| D | megaraid.rst | 17 The advantages, though obvious, are listed for completeness:
|
| /Linux-v5.10/arch/powerpc/include/asm/ |
| D | syscall.h | 62 * In the general case it's not obvious that we must deal with CCR in syscall_set_return_value()
|
| /Linux-v5.10/kernel/time/ |
| D | tick-broadcast-hrtimer.c | 52 * broadcast handler cannot wait for itself to complete for obvious in bc_set_next()
|
| /Linux-v5.10/Documentation/admin-guide/cgroup-v1/ |
| D | pids.rst | 20 pids.max (this is not available in the root cgroup for obvious reasons). The
|
| /Linux-v5.10/Documentation/networking/ |
| D | openvswitch.rst | 157 The basic rule is obvious::
165 This rule does have less-obvious consequences so it is worth working
|
| /Linux-v5.10/include/uapi/linux/raid/ |
| D | md_u.h | 110 /* non-obvious values for 'level' */
|
| /Linux-v5.10/arch/nios2/kernel/ |
| D | module.c | 25 * Modules should NOT be allocated with kmalloc for (obvious) reasons.
|
| /Linux-v5.10/arch/powerpc/sysdev/ |
| D | fsl_gtm.c | 245 /* quite obvious, frequency which is enough for µSec precision */ in gtm_set_timer16()
281 /* quite obvious, frequency which is enough for µSec precision */ in gtm_set_exact_timer16()
|
| /Linux-v5.10/drivers/pcmcia/ |
| D | rsrc_iodyn.c | 92 * potential conflicts, just the most obvious ones. in iodyn_find_io()
|
| /Linux-v5.10/arch/powerpc/boot/ |
| D | mktree.c | 8 * The Right Thing on an LE machine. It's non-obvious, but it should
|
1234567891011
