Searched full:things (Results 1 – 25 of 1729) sorted by relevance
12345678910>>...70
| /linux-3.3/Documentation/power/ |
| D | opp.txt | 111 /* Do things */
117 /* Do cpufreq things */
119 /* Do remaining things */
242 /* do things */
249 /* do other things */
258 /* do things.. */
266 /* do other things */
274 /* do things.. */
282 /* Do things */
296 /* Do other things */
[all …]
|
| D | s2ram.txt | 21 way to debug these things, and it's actually pretty powerful (but
40 holding the power button down, and look at the dmesg output for things
|
| /linux-3.3/Documentation/ |
| D | bus-virt-phys-mapping.txt | 32 things any more complex than necessary, so you can assume that all
36 address, and things are very simple indeed. However, they are that simple
133 buffer), but can be things like a packet buffer in a network card etc.
144 For such memory, you can do things like
196 don't do all that complex things (or rather: the complexity is not so
|
| D | HOWTO | 53 of doing things.
121 not have a stable API within the kernel, including things like:
379 you want to bring up, before you post it to the list. A lot of things
438 again, sometimes things get lost in the huge volume.
454 of a dozen things you should correct. This does _not_ imply that your
464 development environments. Here are a list of things that you can try to
466 Good things to say regarding your proposed changes:
474 Bad things you should avoid saying:
518 The reasons for breaking things up are the following:
587 All of these things are sometimes very hard to do. It can take years to
[all …]
|
| D | ManagementStyle | 52 needs to do is to turn the big and painful ones into small things where
66 things that can't be undone. Don't get ushered into a corner from which
208 Things will go wrong, and people want somebody to blame. Tag, you're it.
230 Chapter 5: Things to avoid
244 Similarly, don't be too polite or subtle about things. Politeness easily
|
| D | stable_api_nonsense.txt | 61 different things can be assumed by the kernel:
97 current interfaces, or figure out a better way to do things. If they do
120 interfaces and do things in improper ways, causing the stability of the
|
| /linux-3.3/Documentation/development-process/ |
| D | 6.Followthrough | 24 process. Life can be made much easier, though, if you keep a few things in
54 understand what the reviewer is trying to say. If possible, fix the things
64 agree with the reviewer, take some time to think things over again. It can
88 What if you've tried to do everything right and things still aren't going
106 things. In particular, there may be more than one tree - one, perhaps,
180 6.3: OTHER THINGS THAT CAN HAPPEN
|
| /linux-3.3/Documentation/trace/ |
| D | ftrace-design.txt | 9 code relies on for proper functioning. Things are broken down into increasing
38 We'll make the assumption below that the symbol is "mcount" just to keep things
65 typically the bare minimum with checking things before returning. That also
143 things.
196 be able to skimp on things saved/restored (usually just registers used to pass
242 You need very few things to get the syscalls tracing in an arch.
348 patching multiple things. First, only functions that we actually want to trace
|
| /linux-3.3/arch/sparc/include/asm/ |
| D | pbm.h | 11 * To put things into perspective, consider sparc64 with a few PCI controllers.
33 /* Now things for the actual PCI bus probes. */
|
| /linux-3.3/arch/x86/include/asm/ |
| D | debugreg.h | 13 /* Define a few things for the status register. We can use this to determine
29 /* Now define a bunch of things for manipulating the control register.
63 /* The second byte to the control register has a few special things.
|
| /linux-3.3/drivers/staging/frontier/ |
| D | README | 28 A sysfs interface is perfect for simple userspace apps to do fun things with
40 cases via a well defined API, but - among other things - is slow, doesn't do
|
| /linux-3.3/arch/blackfin/lib/ |
| D | strncpy.S | 54 * handling the overhead of memset (which is OK when things are big).
62 /* Set things up for memset
|
| /linux-3.3/Documentation/usb/ |
| D | gadget_multi.txt | 24 As one might expect, things one need to do very from system to system.
64 Things are harder with RDNIS and CDC ACM.
96 things don't work as intended before realising Windows have cached
|
| /linux-3.3/drivers/staging/echo/ |
| D | echo.h | 53 things like modem line equalisers and line echo cancellers. There it works very
55 very poorly for things like speech echo cancellation, where the signal level
101 and the environment is not, things will be OK. Clearly, it is easy to tell when
|
| /linux-3.3/Documentation/ABI/ |
| D | README | 57 with userspace developers to ensure that things do not
64 How things move between levels:
|
| /linux-3.3/Documentation/sound/alsa/soc/ |
| D | jack.txt | 17 This is done by splitting the jacks up into three things working
55 update and the set of things to report when the jack is connected.
|
| /linux-3.3/Documentation/sysctl/ |
| D | README | 19 As usual, there are two main things to consider:
45 In fact, there are only four things needed to use these config
|
| /linux-3.3/Documentation/filesystems/caching/ |
| D | cachefiles.txt | 15 (*) Things to avoid.
159 THINGS TO AVOID
162 Do not mount other things within the cache as this will cause problems. The
178 Do not chmod files in the cache. The module creates things with minimal
212 disk space or files is permitted until culling has raised things above
284 they may also contain things like '/' and NUL characters, and so they may not
|
| /linux-3.3/drivers/media/video/zoran/ |
| D | zoran.h | 227 struct zoran_v4l_settings v4l_settings; /* structure with a lot of things to play with */
228 struct zoran_jpg_settings jpg_settings; /* structure with a lot of things to play with */
319 struct zoran_v4l_settings v4l_settings; /* structure with a lot of things to play with */
330 struct zoran_jpg_settings jpg_settings; /* structure with a lot of things to play with */
|
| /linux-3.3/fs/notify/ |
| D | mark.c | 23 * The mark->refcnt tells how many "things" in the kernel currently are
37 * mark->lock protects 2 things, mark->group and mark->inode. You must hold
38 * that lock to dereference either of these things (they could be NULL even with
75 * future. Remember, 10 things might already be referencing this mark, but they
|
| /linux-3.3/Documentation/ia64/ |
| D | aliasing.txt | 22 performance for things like frame buffers.
130 identity mapping. This is obviously safe for things in
133 There may be corner cases of things that are not in kern_memmap,
|
| /linux-3.3/arch/arm/nwfpe/ |
| D | ChangeLog | 26 and needs various things to be re-worked so that we won't
48 user_fp is smaller. This meant that the FPE scribbled on things
|
| /linux-3.3/Documentation/networking/ |
| D | tlan.txt | 36 support such things) will work. I haven't had any solid evidence
107 III. Things to try if you have problems.
|
| /linux-3.3/include/net/irda/ |
| D | discovery.h | 50 * This structure is used in the code for things that are endian neutral
52 * By endian neutral, I mean things that are really an array of bytes,
|
| /linux-3.3/drivers/lguest/ |
| D | segments.c | 3 * which can be used to do funky things with virtual address interpretation.
48 * "Task State Segment" which controls all kinds of delicate things. The
91 * writable by the Guest, so bad things can happen. in fixup_gdt_table()
|
12345678910>>...70