Home
last modified time | relevance | path

Searched refs:upwards (Results 1 – 12 of 12) sorted by relevance

/linux-4.4.14/drivers/video/fbdev/
Datafb_iplan2p2.c44 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()
Datafb_iplan2p4.c44 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()
Datafb_iplan2p8.c51 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/
Dfib_trie.txt76 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/
Dkgdb_asm.S308 move.d internal_stack+1020, $sp ; Use the internal stack which grows upwards
/linux-4.4.14/Documentation/networking/caif/
DLinux-CAIF.txt150 - In order to send data upwards, each layer should do
/linux-4.4.14/drivers/parisc/
DKconfig10 are not found in B1000, C3000, J5000, A500, L1000, N4000 and upwards.
/linux-4.4.14/mm/
DKconfig615 user processes when the stack grows upwards (currently only on parisc
/linux-4.4.14/Documentation/laptops/
Dlaptop-mode.txt571 # (2.6.7 upwards)
/linux-4.4.14/Documentation/
Dkmemcheck.txt300 of calls, we move upwards to see where "from" was allocated or initialized,
/linux-4.4.14/Documentation/filesystems/
Dxfs-delayed-logging-design.txt408 vs two dirty cachelines except for the fact I've seen upwards of 80,000 log
/linux-4.4.14/Documentation/s390/
DDebugging390.txt63 point format compliant on G5 upwards & a Floating point control reg (FPC)