| /openthread-3.6.0/third_party/tcplp/bsdtcp/cc/ |
| D | cc_module.h | 58 #define CCV(ccv, what) (ccv)->ccvc.tcp->what argument
|
| /openthread-3.6.0/.github/ISSUE_TEMPLATE/ |
| D | bug_report.md | 6 **Describe the bug** A clear and concise description of what the bug is.
15 **Expected behavior** A clear and concise description of what you expected to happen.
|
| D | feature_request.md | 6 …st related to a problem? Please describe.** A clear and concise description of what the problem is.
8 **Describe the solution you'd like** A clear and concise description of what you want to happen.
|
| /openthread-3.6.0/third_party/mbedtls/repo/library/ |
| D | aesni.c | 48 int mbedtls_aesni_has_support( unsigned int what ) in mbedtls_aesni_has_support() argument
63 return( ( c & what ) != 0 ); in mbedtls_aesni_has_support()
|
| /openthread-3.6.0/ |
| D | STYLE_GUIDE.md | 123 - File names should match the names and types of what is described in the file. If a file contains …
124 - File contents and names should be limited in the scope of what they contain. It may also be possi…
167 - Detail what the various source and header files are and how they fit into the broader context.
168 - Detail what the various C++ namespaces are.
169 - Detail what the constants, C preprocessor definitions, and enumerations are.
170 - Detail what the globals are and how they are to be used.
171 …- Detail what the free function and object / class methods are and how they are to be used, what t…
174 - Briefly describes what it is and what it does.
175 - Describes in detail, optionally, what it is and what it does.
|
| D | CODE_OF_CONDUCT.md | 17 - Focusing on what is best not just for us as individuals, but for the overall community
|
| /openthread-3.6.0/third_party/mbedtls/repo/include/mbedtls/ |
| D | aesni.h | 62 int mbedtls_aesni_has_support( unsigned int what );
|
| /openthread-3.6.0/third_party/build_gn/toolchain/ |
| D | BUILD.gn | 42 # overrides it (in which case {{output_extension}} will be what the target
46 # it (in which case {{output_dir}} will be what the target specifies).
|
| /openthread-3.6.0/third_party/mbedtls/repo/docs/proposed/ |
| D | psa-driver-integration-guide.md | 43 <!-- TODO: what if the driver is provided as C source code? -->
45 <!-- TODO: what about additional include files? -->
|
| D | psa-driver-developer-guide.md | 25 …river description file declares which functions the driver implements and what cryptographic mecha…
|
| /openthread-3.6.0/third_party/mbedtls/repo/docs/architecture/testing/ |
| D | test-framework.md | 13 Each test case has a description which succinctly describes for a human audience what the test does…
20 …Rationale: 66 characters is what our various tools assume (leaving room for 14 more characters on …
33 …opt.sh` has a description which succinctly describes for a human audience what the test does. The …
|
| D | psa-storage-format-testing.md | 27 If the test passes with version V, this means that the test data is consistent with what the implem…
29 … on version W with the same data that proves that version W can read back what version V wrote. Fr…
85 …ally based on an enumeration of available constants and some knowledge of what attributes (sizes, …
|
| D | invasive-testing.md | 9 This is a test strategy document, not a test plan. A description of exactly what is tested is out o…
20 This document currently focuses on data structure manipulation and storage, which is what the crypt…
42 > * on top of stdio. It expects to know what the stdio name of a file is
214 | Correctness | ! Difficult to ensure that what we test is what we run |
254 * Writing reliable debugger scripts is hard. We need to have confidence that we're testing what we …
|
| /openthread-3.6.0/third_party/mbedtls/repo/.github/ |
| D | pull_request_template.md | 21 If there is any API change, what's the incentive and logic for it.
|
| /openthread-3.6.0/third_party/mbedtls/repo/tests/suites/ |
| D | test_suite_mps.function | 59 /* Consume exactly what's available */
104 /* Consume exactly what's available */
218 * of the consumer exceeds what has been provided by the producer, and when
335 * - The consumer asks for more data than what's available.
362 /* Ask for more than what's available. */
457 * - The consumer has asked for more than what's available, so the
484 /* Ask for more than what's available. */
685 /* Ask for more than what's available. */
932 /* Check if output is in accordance with what was written */
976 * - The consumer asks for more data than what's available
|
| D | test_suite_memory_buffer_alloc.function | 144 * bytes, and makes it hard to know what the reported size will be, so
|
| D | test_suite_psa_crypto_storage_format.function | 184 * can read back what this version wrote. */
|
| D | test_suite_psa_its.function | 4 * on top of stdio. It expects to know what the stdio name of a file is
|
| D | test_suite_asn1parse.function | 241 * valid depending on what the trailing garbage is. */
250 * we wouldn't know what to parse the input as.
|
| D | test_suite_entropy.function | 477 // Determine what should have happened with manual entropy internal logic
|
| D | test_suite_pkcs1_v15.function | 241 /* Check that the output in invalid cases is what the default
|
| /openthread-3.6.0/tests/unit/ |
| D | README.md | 16 To see what tests are available in OpenThread:
|
| /openthread-3.6.0/third_party/mbedtls/repo/tests/scripts/ |
| D | test_zeroize.gdb | 30 # problem is that a compiler would typically remove what it considers to be
|
| /openthread-3.6.0/tools/harness-automation/autothreadharness/ |
| D | harness_case.py | 66 def wait_until(what, times=-1): argument
80 if what() is True:
|
| /openthread-3.6.0/third_party/mbedtls/repo/ |
| D | README.md | 82 In case you find that you need to do something else as well, please let us know what, so we can add…
197 - [What external dependencies does Mbed TLS rely on?](https://tls.mbed.org/kb/development/what-ex…
|
