Searched full:just (Results 1 – 25 of 716) sorted by relevance
12345678910>>...29
| /Documentation/media/uapi/rc/ |
| D | lirc-get-features.rst | 52 Unused. Kept just to avoid breaking uAPI.
58 Unused. Kept just to avoid breaking uAPI.
75 Unused. Kept just to avoid breaking uAPI.
116 Unused. Kept just to avoid breaking uAPI.
143 Unused. Kept just to avoid breaking uAPI.
163 Unused. Kept just to avoid breaking uAPI.
169 Unused. Kept just to avoid breaking uAPI.
185 Unused. Kept just to avoid breaking uAPI.
192 Unused. Kept just to avoid breaking uAPI.
|
| /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/vm/ |
| D | active_mm.rst | 21 > discussed on the mailing lists---I just returned from vacation and
29 anonymous address space we just leave the previous address space
70 more. "init_mm" should be considered just a "lazy context when no other
71 context is available", and in fact it is mainly used just at bootup when
76 should generally just do
84 Anyway, I put a pre-patch-2.3.13-1 on ftp.kernel.org just a moment ago,
|
| /Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-elog | 46 Currently just "0x00 PEL" - platform error log.
51 <16kb, often just hundreds of bytes and
60 operations (currently just acknowledge).
|
| /Documentation/dev-tools/ |
| D | sparse.rst | 33 ends up looking just like integers to gcc.
35 Quite frankly, you don't need the enum there. The above all really just
38 So the simpler way is to just do::
84 Once you have it, just do::
|
| /Documentation/scheduler/ |
| D | sched-stats.rst | 111 cpu was just becoming idle
113 load did not require balancing when the cpu was just becoming idle
115 tasks and failed, when the cpu was just becoming idle
117 load_balance() in this domain when the cpu was just becoming idle
120 target task was cache-hot when just becoming idle
122 find a busier queue while the cpu was just becoming idle
124 was just becoming idle but no busier group was found
|
| /Documentation/maintainer/ |
| D | pull-requests.rst | 30 have just created. It is recommended that you choose a meaningful tag name,
62 not just make sense to me, but make sense as a historical record
68 diffstat anyway, and if you didn't mention it, I'll just be extra
70 (or even bug-fixes, but ones that look scary), explain not just
78 tag just a placeholder with nothing interesting in it, and describe
81 And yes, I will edit the message. Partly because I tend to do just
123 The tag message format is just like a git commit id. One line at the top
|
| /Documentation/ |
| D | bus-virt-phys-mapping.txt | 50 Now, just as an example, on the PReP (PowerPC Reference Platform), the
71 where all the addresses actually point to the same thing. It's just seen
130 address in some cases, it's just not very often in normal code. The physical
144 of a video graphics card it can be normal DRAM that is just used for a frame
152 just dereference a pointer. (Sadly, on x86 it **is** in the same memory space,
153 so on x86 it actually works to just deference a pointer, but it's not
191 OK, that just about covers the basics of accessing IO portably. Questions?
|
| /Documentation/usb/ |
| D | functionfs.rst | 5 From kernel point of view it is just a composite function with some
55 just one function with any name.
59 parameter's value is just a one-element list, then the behaviour
|
| /Documentation/networking/ |
| D | x25.txt | 26 Just when you thought that it could not become more confusing, another
34 parties are welcome to subscribe to it. Just send a message to
|
| /Documentation/filesystems/ |
| D | inotify.txt | 8 --Deleted obsoleted interface, just refer to manpages for user interface.
48 versus just one. It is a lot messier in the kernel. A single, linear
60 scales to 1000s of directories, juggling 1000s of fd's just does not seem
|
| D | bfs.txt | 23 You can simplify mounting by just typing:
47 Just in case, you can verify that you have done the right thing by checking
|
| D | mandatory-locking.txt | 54 interface for applying locks just as if they were normal, advisory locks.
97 just mandatory locks. That would appear to contravene POSIX.1.
112 below are just as valid as any others, so long as the main points seem to
149 Those which modify a file's contents, not just the inode. That gives read(),
157 added, as a lock can specify just "the whole file", rather than a specific
|
| D | porting.rst | 136 FS_LITTER is gone - just remove it from fs_flags.
143 went in - and hadn't been documented ;-/). Just remove it from fs_flags
202 just takes the superblock and inode number as arguments and does the
258 FS_NOMOUNT is gone. If you use it - just set SB_NOUSER in flags
397 initialize the former in inode_init_always(), so just leave it alone in
445 ->get_sb() is gone. Switch to use of ->mount(). Typically it's just
447 the function type. If you were doing it manually, just switch from setting
506 ->lookup() do *not* take struct nameidata anymore; just the flags.
591 for embedded ("fast") symlinks just set inode->i_link to wherever the
642 ->put_link() is gone - just give the destructor to set_delayed_call()
[all …]
|
| /Documentation/ABI/testing/ |
| D | configfs-usb-gadget-phonet | 6 This item contains just one readonly attribute: ifname.
|
| D | configfs-usb-gadget-serial | 6 This item contains just one readonly attribute: port_num.
|
| D | configfs-usb-gadget-acm | 6 This item contains just one readonly attribute: port_num.
|
| D | configfs-usb-gadget-obex | 6 This item contains just one readonly attribute: port_num.
|
| D | sysfs-class-fpga-region | 9 just error code -ENOENT in case compat_id is not used.
|
| /Documentation/devicetree/bindings/ |
| D | writing-bindings.txt | 25 - DON'T create nodes just for the sake of instantiating drivers. Multi-function
45 - DON'T redefine common properties. Just reference the definition and define
|
| /Documentation/firmware-guide/acpi/ |
| D | method-customizing.rst | 15 or just for debugging purposes.
41 just run "cat /sys/firmware/acpi/tables/DSDT > /tmp/dsdt.dat"
69 We just need to create the ASL code of the method we want to
|
| /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/admin-guide/ |
| 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/ABI/removed/ |
| D | sysfs-class-rfkill | 10 claim just control over a single rfkill instance.
|
| /Documentation/m68k/ |
| D | buddha-driver.rst | 13 The Autoconfiguration has been implemented just as Commodore
29 Setting the base address should be done in two steps, just
35 address just written. Make sure $4a is written before $48,
112 The IDE ports are fed by the address lines A2 to A4, just as
199 Buddha acts just like a Catweasel Z-II with no device
|
12345678910>>...29