HomeSort by relevance Sort by last modified time
    Searched full:sha1s (Results 1 - 8 of 8) sorted by null

  /bootable/recovery/tests/component/
applypatch_test.cpp 285 std::vector<char*> sha1s; local
286 sha1s.push_back(&bad_sha1_a[0]);
287 sha1s.push_back(&old_sha1[0]);
294 sha1s.data(),
305 sha1s.data(),
313 std::vector<char*> sha1s; local
314 sha1s.push_back(&bad_sha1_a[0]);
315 sha1s.push_back(&old_sha1[0]);
321 sha1s.data(),
331 sha1s.data()
340 std::vector<char*> sha1s; local
369 std::vector<char*> sha1s; local
    [all...]
  /bootable/recovery/applypatch/
main.cpp 50 // into the new parallel arrays *sha1s and *files.Returns true on
52 static bool ParsePatchArgs(int argc, char** argv, std::vector<char*>* sha1s,
69 sha1s->push_back(argv[i]);
121 std::vector<char*> sha1s; local
123 if (!ParsePatchArgs(argc-5, argv+5, &sha1s, &files)) {
136 patch_ptrs.size(), sha1s.data(),
applypatch.cpp 96 // repeated with different sha1s. Will return 0 on success.
531 // It's okay to specify no sha1s; the check will pass if the
533 // partitions, where the filename encodes the sha1s; no need to
    [all...]
  /external/boringssl/src/util/bot/
vs_toolchain.py 65 """Load a list of SHA1s corresponding to the toolchains that we want installed
  /external/v8/build/android/play_services/
update_test.py 271 file. The sha1s will be copied to the config directory
335 # TODO(dgn) should we use real sha1s? comparison with the real sha1 is
  /bootable/recovery/updater/
install.cpp 1261 char** sha1s = ReadVarArgs(state, argc-1, argv+1); local
    [all...]
  /external/v8/build/
vs_toolchain.py 279 """Load a list of SHA1s corresponding to the toolchains that we want installed
  /external/v8/gypfiles/
vs_toolchain.py 280 """Load a list of SHA1s corresponding to the toolchains that we want installed

Completed in 1001 milliseconds