Searched full:matters (Results 1 – 15 of 15) sorted by relevance
20 the order of the nodes matters. The first node for gpio1 will be used
30 Exercise voting rights on important matters discussed within the TSC,51 Provide guidance and oversight on technical matters, ensuring alignment with
41 * Right to approach any member of the community with matters they believe
22 * This matters if you're doing in-application
169 * - image_load_address: skip (only matters for PIC code) in boot_read_bank_header()
782 * memory alignment often matters.793 * memory alignment often matters.
128 /* This is the byte which matters */
181 EC_SPI_FRAME_START, /* This is the byte which matters */
529 # If several match then the last one wins. This matters for instances633 # matters so we need to be careful about how we order the processing641 # Another example of when the order matters is the reading and writing
694 * but has no assertions in place to check this. If this matters, it may be
746 The order of the ``include()`` calls in your :file:`board.cmake` matters. The
2883 # itself that matters.2893 # property on 'node' itself that matters
212 For non-bool/tristate symbols, it only matters whether the visibility is n or788 the value when the configuration is loaded matters. This avoids surprises2964 # due to tricky Python semantics. The order matters.6576 # due to tricky Python semantics. The order matters.
2150 The order that filters appear in the above list matters.
