Searched refs:upwards (Results 1 – 12 of 12) sorted by relevance
| /linux-4.4.14/drivers/video/fbdev/ |
| D | atafb_iplan2p2.c | 44 u_int upwards = (dy < sy) || (dy == sy && dx < sx); in atafb_iplan2p2_copyarea() local
50 if (upwards) { in atafb_iplan2p2_copyarea()
105 if (upwards) { in atafb_iplan2p2_copyarea()
|
| D | atafb_iplan2p4.c | 44 u_int upwards = (dy < sy) || (dy == sy && dx < sx); in atafb_iplan2p4_copyarea() local
50 if (upwards) { in atafb_iplan2p4_copyarea()
105 if (upwards) { in atafb_iplan2p4_copyarea()
|
| D | atafb_iplan2p8.c | 51 u_int upwards = (dy < sy) || (dy == sy && dx < sx); in atafb_iplan2p8_copyarea() local
57 if (upwards) { in atafb_iplan2p8_copyarea()
112 if (upwards) { in atafb_iplan2p8_copyarea()
|
| /linux-4.4.14/Documentation/networking/ |
| D | fib_trie.txt | 76 it is run to optimize and reorganize. It will walk the trie upwards
127 and we backtrack upwards through the trie trying to find a longest matching
|
| /linux-4.4.14/arch/cris/arch-v32/kernel/ |
| D | kgdb_asm.S | 308 move.d internal_stack+1020, $sp ; Use the internal stack which grows upwards
|
| /linux-4.4.14/Documentation/networking/caif/ |
| D | Linux-CAIF.txt | 150 - In order to send data upwards, each layer should do
|
| /linux-4.4.14/drivers/parisc/ |
| D | Kconfig | 10 are not found in B1000, C3000, J5000, A500, L1000, N4000 and upwards.
|
| /linux-4.4.14/mm/ |
| D | Kconfig | 615 user processes when the stack grows upwards (currently only on parisc
|
| /linux-4.4.14/Documentation/laptops/ |
| D | laptop-mode.txt | 571 # (2.6.7 upwards)
|
| /linux-4.4.14/Documentation/ |
| D | kmemcheck.txt | 300 of calls, we move upwards to see where "from" was allocated or initialized,
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | xfs-delayed-logging-design.txt | 408 vs two dirty cachelines except for the fact I've seen upwards of 80,000 log
|
| /linux-4.4.14/Documentation/s390/ |
| D | Debugging390.txt | 63 point format compliant on G5 upwards & a Floating point control reg (FPC)
|