Searched full:expectations (Results 1 – 25 of 26) sorted by relevance
12
21 Driver Implementation Expectations43 Channel State Machine Expectations argument
3 # See root CMakeLists.txt for description and expectations of these macros
12 * expectations of the memory region used. If a board specific variant is
16 * common expectations and usage.
1 .. _contributor-expectations:3 Contributor Expectations264 .. _reviewer-expectations:266 Reviewer Expectations
29 :ref:`contributor-expectations`
501 See the :ref:`contributor-expectations` for a more complete discussion of502 contributor and reviewer expectations.
20 this correctly without arbitrary expectations of maximum latency requires that
11 following expectations:
102 not follow the :ref:`expectations <reviewer-expectations>` and the guidelines171 :ref:`expectations <reviewer-expectations>` from reviewers and seek reviews189 that does not follow the project expectations.
81 project's strategic objectives and expectations.
38 … Expectations](https://docs.zephyrproject.org/latest/contribute/contributor_expectations.html)
32 * expectations and how to notify the client when the request
44 The expectations above affect selection of other features; for example
21 Below are the guidelines for the requirements repository and the expectations of the safety
122 Test result expectations501 Expectations subsection507 test. If the config :kconfig:option:`CONFIG_ZTEST_ASSERT_VERBOSE` is 0, the expectations will only …510 For example, if the following expectations fail:
55 meet our expectations as we would like to route I2C_0's SDA signal to GPIO_33
32 Building and expectations
16 * of some of the registers. Check that our expectations are met.
221 * expectations and how to notify the client when the request
126 * as a parameter matches these expectations.
187 * its expectations (e.g. supplying it with some 3.3V Nucleo board), in hd44780_ic_initialize()
336 * instructions on synchronous expectations and how to notify the
1203 :ref:`expectations <contributor-expectations>`.
