Searched refs:tester (Results 1 – 13 of 13) sorted by relevance
94 u32 tester; member197 remote->data.tester = 0; in keyspan_check_data()220 remote->data.tester = remote->data.tester >> 14; in keyspan_check_data()225 remote->data.tester = remote->data.tester >> 1; in keyspan_check_data()254 remote->data.tester = remote->data.tester >> 5; in keyspan_check_data()258 remote->data.tester = remote->data.tester >> 6; in keyspan_check_data()275 remote->data.tester = remote->data.tester >> 5; in keyspan_check_data()279 remote->data.tester = remote->data.tester >> 6; in keyspan_check_data()293 remote->data.tester = remote->data.tester >> 5; in keyspan_check_data()297 remote->data.tester = remote->data.tester >> 6; in keyspan_check_data()[all …]
62 tristate "XZ decompressor tester"
172 codice nelle mani di un gruppo di *tester* molto più esteso. Anche se avete175 E, ovviamente, dove ci sono *tester*, ci saranno anche dei rapporti su
293 quella funzione. Revisori e tester vogliono invece avere accesso alle
570 Quando si riceve una email sulla lista di discussione da un tester o
154 void (*tester)(int cg_fd, struct sockmap_options *opt); member1879 t.tester(cg_fd, opt); in __test_selftests()
359 - Tested-by: ``Tester <tester@mail>``
559 Both Tested-by and Reviewed-by tags, once received on mailing list from tester
789 tristate "Ring buffer benchmark stress tester"
739 tristate "Powerpc64 vpmsum hardware acceleration tester"
161 If you are a developer or tester and want to ensure the exported
2486 tristate "kmod stress tester"
1424 D: /proc/cpuinfo, reboot on panic , kernel pre-patch tester ;)
Completed in 44 milliseconds