Searched full:obviously (Results 1 – 25 of 290) sorted by relevance
12345678910>>...12
86 hardware, although under the terms of the GPL you're obviously103 hardware, although under the terms of the GPL you're obviously128 hardware, although under the terms of the GPL you're obviously
22 address space is obviously better performed by flushing the36 There is obviously no way the kernel can know all these things,
44 - however, we obviously need to keep track of which address space we49 non-NULL) the active_mm obviously always has to be the same as the real
4 - Binding docs for devices that are obviously used via device
25 * This is obviously not a great place for this, but we want to be
19 ( rsp is obviously invariant across normal function calls. (gcc can 'merge'43 ( here too esp is obviously invariant across normal function calls. eflags375 * %gs here and obviously can not use %gs itself to access per-CPU data.
97 * current can obviously not fork at the same time. If it's shared in ksys_ioperm()128 * to keep it obviously correct: in ksys_ioperm()
48 * obviously.
27 degrees C. The datasheet is rather poor and obviously inaccurate
23 (but you need NFS file system support obviously).
11 module to instantiate the right I2C chip on the bus. Obviously, a driver
59 /* this must (obviously) be the last on in the enum */
55 * The cdrom layer call failed or returned obviously bogus value? in udf_get_last_block()
11 /// obviously redundant, the compiler's dead-store elimination pass will make
11 In order to access /stand partition under Linux you obviously need to
26 * relevant is mentioned in GCC 8 release notes and nothing obviously relevant
18 information and act upon it. Obviously, the OS has to know about
54 # - this obviously affects the randomness within the packet
27 * obviously not be running from flash. The __xipram is therefore marking
7 * It's obviously not thread-safe. Sue me. But it's quite
24 * NOTE! We need to allow non-page-aligned mappings too: we will obviously
84 * obviously bogus ones here. We replace them in perf_callchain_kernel()
321 /* See if icount is obviously wrong. */ in xchk_fscounters()325 /* See if fdblocks is obviously wrong. */ in xchk_fscounters()
67 * we are affected is that we will have an obviously bogus
21 handler (sometimes measured in milliseconds). Obviously this is a problem if
