Searched refs:two (Results 1 – 6 of 6) sorted by relevance
/system/core/libbacktrace/ |
D | backtrace_testlib.c | 19 int test_level_four(int one, int two, int three, int four, in test_level_four() argument 27 return one + two + three + four; in test_level_four() 30 int test_level_three(int one, int two, int three, int four, in test_level_three() argument 32 return test_level_four(one+3, two+6, three+9, four+12, callback_func, data) + 3; in test_level_three() 35 int test_level_two(int one, int two, int three, int four, in test_level_two() argument 37 return test_level_three(one+2, two+4, three+6, four+8, callback_func, data) + 2; in test_level_two() 40 int test_level_one(int one, int two, int three, int four, in test_level_one() argument 42 return test_level_two(one+1, two+2, three+3, four+4, callback_func, data) + 1; in test_level_one()
|
/system/core/adb/ |
D | OVERVIEW.TXT | 61 There are essentially two kinds of services that a client can talk to. 125 or emulator. There are currently two kinds of transports:
|
D | SYNC.TXT | 54 The remote file name is split into two parts separated by the last
|
D | protocol.txt | 201 The remote side connection will be implemented as two threads (one for 227 The bootloader will support two streams. A "bootloader:debug" stream,
|
/system/core/libutils/ |
D | README | 110 defines two namespaces: 174 an overlay package. To translate between the two, a resource ID mapping
|
/system/media/camera/docs/ |
D | html.mako | 110 # insert line breaks after every two \n\n
|