Home
last modified time | relevance | path

Searched full:obvious (Results 1 – 25 of 270) sorted by relevance

1234567891011

/Linux-v6.1/Documentation/ia64/
Dia64.rst42 * Hardly any performance tuning has been done. Obvious targets
44 obvious targets include making sure we don't flush the TLB
/Linux-v6.1/Documentation/process/
Dmanagement-style.rst27 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
Dmaintainer-tip.rst488 /* This condition is not obvious without a comment */
499 Comments should be added where the operation is not obvious. Documenting
500 the obvious is just a distraction::
511 Instead, comments should explain the non-obvious details and document
/Linux-v6.1/Documentation/mm/
Dmultigen_lru.rst19 * Fast paths to make obvious choices
40 additional factors stand out. But obvious choices might not be good
Dovercommit-accounting.rst8 Heuristic overcommit handling. Obvious overcommits of address
Dactive_mm.rst32 The obvious use for a "anonymous address space" is any thread that
/Linux-v6.1/arch/mips/sni/
Deisa.c16 * Now use a platform device, since that's the obvious choice. */
/Linux-v6.1/drivers/eisa/
Dvirtual_root.c26 * Now use a platform device, since that's the obvious choice. */
/Linux-v6.1/Documentation/sh/
Dregister-banks.rst21 in mind when writing code that utilizes these banked registers, for obvious
/Linux-v6.1/Documentation/kbuild/
DKconfig.recursion-issue-0137 # obvious that an easy to solution to this problem should just be the removal
DKconfig.recursion-issue-0218 # A perhaps not so obvious implication of this is that, if semantics on these
/Linux-v6.1/Documentation/maintainer/
Dmodifying-patches.rst16 name, all enclosed in square brackets, is noticeable enough to make it obvious
/Linux-v6.1/drivers/cxl/
Dcxlpci.h13 * "DVSEC" redundancies removed. When obvious, abbreviations may be used.
/Linux-v6.1/Documentation/driver-api/gpio/
Dusing-gpio.rst6 as such are normally not user facing abstractions. The most obvious, natural
/Linux-v6.1/arch/x86/include/asm/
Dibt.h14 * Esp. that latter one is a bit non-obvious, but some code like compressed,
/Linux-v6.1/Documentation/userspace-api/
Dno_new_privs.rst6 its parent did not have. The most obvious examples are setuid/setgid
/Linux-v6.1/drivers/gpu/drm/panel/
Dpanel-samsung-atna33xc20.c152 * obvious if we try to enable again without a power cycle (see the in atana33xc20_disable()
180 * non-obvious. in atana33xc20_enable()
/Linux-v6.1/Documentation/scsi/
Dmegaraid.rst17 The advantages, though obvious, are listed for completeness:
/Linux-v6.1/arch/mips/include/asm/
Dunroll.h23 * up until 8.0 tend to miss obvious constants & cause \
/Linux-v6.1/arch/powerpc/include/asm/
Dsyscall.h78 * In the general case it's not obvious that we must deal with in syscall_set_return_value()
/Linux-v6.1/kernel/time/
Dtick-broadcast-hrtimer.c52 * broadcast handler cannot wait for itself to complete for obvious in bc_set_next()
/Linux-v6.1/Documentation/admin-guide/cgroup-v1/
Dpids.rst20 pids.max (this is not available in the root cgroup for obvious reasons). The
/Linux-v6.1/Documentation/networking/
Dopenvswitch.rst157 The basic rule is obvious::
165 This rule does have less-obvious consequences so it is worth working
/Linux-v6.1/rust/alloc/vec/
Dis_zero.rs57 // Because this is generated as a runtime check, it's not obvious that in is_zero()
/Linux-v6.1/include/uapi/linux/raid/
Dmd_u.h110 /* non-obvious values for 'level' */

1234567891011