| /linux/Documentation/process/ |
| H A 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/Documentation/litmus-tests/ |
| H A D | README | 46 the obvious lock acquisitions and releases.
51 obvious lock acquisitions and releases.
|
| /linux/arch/mips/sni/ |
| H A D | eisa.c | 16 * Now use a platform device, since that's the obvious choice. */
|
| /linux/drivers/eisa/ |
| H A D | virtual_root.c | 26 * Now use a platform device, since that's the obvious choice. */
|
| /linux/drivers/md/dm-vdo/ |
| H A D | priority-table.h | 13 * are small non-negative integer values. It implements the obvious priority queue operations of
|
| /linux/Documentation/arch/sh/ |
| H A D | register-banks.rst | 21 in mind when writing code that utilizes these banked registers, for obvious
|
| /linux/Documentation/kbuild/ |
| H A D | Kconfig.recursion-issue-01 | 37 # obvious that an easy solution to this problem should just be the removal
|
| H A D | Kconfig.recursion-issue-02 | 18 # A perhaps not so obvious implication of this is that, if semantics on these
|
| /linux/Documentation/maintainer/ |
| H A D | modifying-patches.rst | 16 name, all enclosed in square brackets, is noticeable enough to make it obvious
|
| /linux/Documentation/bpf/ |
| H A D | graph_ds_impl.rst | 110 object was ``free``'d with ``bpf_obj_drop`` the answer is obvious: the verifier
116 obvious. The verifier could enforce the same semantics as for ``bpf_obj_drop``,
|
| /linux/Documentation/driver-api/gpio/ |
| H A D | using-gpio.rst | 6 as such are normally not user facing abstractions. The most obvious, natural
|
| /linux/Documentation/userspace-api/ |
| H A D | no_new_privs.rst | 6 its parent did not have. The most obvious examples are setuid/setgid
|
| /linux/Documentation/mm/ |
| H A D | overcommit-accounting.rst | 8 Heuristic overcommit handling. Obvious overcommits of address
|
| H A D | multigen_lru.rst | 19 * Fast paths to make obvious choices
40 additional factors stand out. But obvious choices might not be good
|
| H A D | active_mm.rst | 36 The obvious use for a "anonymous address space" is any thread that
|
| /linux/arch/x86/include/asm/ |
| H A D | ibt.h | 14 * Esp. that latter one is a bit non-obvious, but some code like compressed,
|
| /linux/Documentation/scsi/ |
| H A D | megaraid.rst | 17 The advantages, though obvious, are listed for completeness:
|
| /linux/arch/mips/include/asm/ |
| H A D | unroll.h | 23 * up until 8.0 tend to miss obvious constants & cause \
|
| /linux/Documentation/networking/ |
| H A D | openvswitch.rst | 157 The basic rule is obvious::
165 This rule does have less-obvious consequences so it is worth working
|
| /linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | pids.rst | 20 pids.max (this is not available in the root cgroup for obvious reasons). The
|
| /linux/arch/powerpc/include/asm/ |
| H A D | syscall.h | 88 * In the general case it's not obvious that we must deal with in syscall_set_return_value()
|
| /linux/arch/powerpc/sysdev/ |
| H A 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/arch/x86/kernel/cpu/ |
| H A D | topology_ext.c | 82 * It really would have been too obvious to make the domain in topo_subleaf()
|
| /linux/arch/arm/lib/ |
| H A D | div64.S | 187 @ eq -> division by 1: obvious enough...
|
| /linux/arch/powerpc/boot/ |
| H A D | mktree.c | 8 * The Right Thing on an LE machine. It's non-obvious, but it should
|