Searched full:just (Results 1 – 25 of 839) sorted by relevance
12345678910>>...34
| /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 …]
|
| /Documentation/mm/ |
| D | active_mm.rst | 25 > discussed on the mailing lists---I just returned from vacation and
33 anonymous address space we just leave the previous address space
74 more. "init_mm" should be considered just a "lazy context when no other
75 context is available", and in fact it is mainly used just at bootup when
80 should generally just do
88 Anyway, I put a pre-patch-2.3.13-1 on ftp.kernel.org just a moment ago,
|
| /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.
144 Unused. Kept just to avoid breaking uAPI.
160 Unused. Kept just to avoid breaking uAPI.
167 Unused. Kept just to avoid breaking uAPI.
|
| /Documentation/admin-guide/ |
| D | cputopology.rst | 46 7) topology_sibling_cpumask: just the given CPU
47 8) topology_core_cpumask: just the given CPU
48 9) topology_cluster_cpumask: just the given CPU
49 10) topology_die_cpumask: just the given CPU
50 11) topology_book_cpumask: just the given CPU
51 12) topology_drawer_cpumask: just the given CPU
|
| D | mono.rst | 8 This will allow you to execute Mono-based .NET binaries just like any
21 Once the Mono CLR support has been installed, just check that
|
| /Documentation/scheduler/ |
| D | sched-stats.rst | 116 cpu was just becoming idle
118 load did not require balancing when the cpu was just becoming idle
120 tasks and failed, when the cpu was just becoming idle
122 sched_balance_rq() in this domain when the cpu was just becoming idle
125 target task was cache-hot when just becoming idle
127 find a busier queue while the cpu was just becoming idle
129 was just becoming idle but no busier group was found
|
| /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::
|
| /Documentation/maintainer/ |
| D | pull-requests.rst | 28 have just created. It is recommended that you choose a meaningful tag name,
60 not just make sense to me, but make sense as a historical record
66 diffstat anyway, and if you didn't mention it, I'll just be extra
68 (or even bug-fixes, but ones that look scary), explain not just
76 tag just a placeholder with nothing interesting in it, and describe
79 And yes, I will edit the message. Partly because I tend to do just
121 The tag message format is just like a git commit id. One line at the top
|
| /Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-elog | 47 Currently just "0x00 PEL" - platform error log.
52 <16kb, often just hundreds of bytes and
61 operations (currently just acknowledge).
|
| /Documentation/leds/ |
| D | leds-cht-wcove.rst | 35 This is just like how blinking works in the LED subsystem,
37 while blinking. Breathing on this hw really is just a variant
|
| /Documentation/devicetree/bindings/ |
| D | example-schema.yaml | 59 # 'const' is just a special case of an enum with a single possible value
79 # Cases that have only a single entry just need to express that with maxItems
89 # just skip the xxx-names.
120 # The core checks this is a boolean, so just have to list it here to be
178 description: Child nodes are just another property from a json-schema
213 # If the conditionals become too unweldy, then it may be better to just split
|
| /Documentation/networking/ |
| D | x25.rst | 28 Just when you thought that it could not become more confusing, another
36 parties are welcome to subscribe to it. Just send a message to
|
| /Documentation/ABI/testing/ |
| D | configfs-usb-gadget-phonet | 6 This item contains just one readonly attribute: ifname.
|
| D | configfs-usb-gadget-obex | 6 This item contains just one readonly attribute: port_num.
|
| D | configfs-usb-gadget-serial | 6 This item contains just one readonly attribute: port_num.
|
| D | sysfs-bus-iio-humidity | 9 In some devices, this is just a switch in which case 0 = OFF,
|
| D | sysfs-class-fpga-region | 9 just error code -ENOENT in case compat_id is not used.
|
| D | configfs-usb-gadget-acm | 6 This item contains just one readonly attribute: port_num.
|
| /Documentation/driver-api/thermal/ |
| D | exynos_thermal_emulation.rst | 35 change the value to updated one and just use last succeessful value
37 termerpature only. Just one interface makes it more simply to use.
|
| /Documentation/filesystems/ |
| D | inotify.rst | 13 - Deleted obsoleted interface, just refer to manpages for user interface.
57 versus just one. It is a lot messier in the kernel. A single, linear
69 scales to 1000s of directories, juggling 1000s of fd's just does not seem
|
| D | bfs.rst | 26 You can simplify mounting by just typing::
50 Just in case, you can verify that you have done the right thing by checking
|
| D | porting.rst | 142 FS_LITTER is gone - just remove it from fs_flags.
149 went in - and hadn't been documented ;-/). Just remove it from fs_flags
208 just takes the superblock and inode number as arguments and does the
264 FS_NOMOUNT is gone. If you use it - just set SB_NOUSER in flags
403 initialize the former in inode_init_always(), so just leave it alone in
451 ->get_sb() is gone. Switch to use of ->mount(). Typically it's just
453 the function type. If you were doing it manually, just switch from setting
512 ->lookup() do *not* take struct nameidata anymore; just the flags.
597 for embedded ("fast") symlinks just set inode->i_link to wherever the
648 ->put_link() is gone - just give the destructor to set_delayed_call()
[all …]
|
| /Documentation/usb/ |
| D | functionfs.rst | 8 From kernel point of view it is just a composite function with some
60 just one function with any name.
64 parameter's value is just a one-element list, then the behaviour
|
| /Documentation/arch/powerpc/ |
| D | kasan.txt | 38 One approach is just to give up on inline instrumentation. This way boot-time
39 checks can be delayed until after the MMU is set is up, and we can just not
|
| /Documentation/firmware-guide/acpi/ |
| D | non-d0-probe.rst | 12 beyond just powering on the said device.
23 there's a problem with the device, the driver likely probes just fine but the
|
12345678910>>...34