Searched refs:who (Results 1 – 25 of 40) sorted by relevance
12
| /Zephyr-Core-3.7.0/doc/security/standards/ |
| D | index.rst | 8 of the problem and who to properly respond it.
|
| D | etsi-303645.rst | 26 - user who has the highest-privilege level possible for a user of the device,
51 - natural person who is acting for purposes that are outside her/his trade,
106 - user who owns or who purchased the device.
713 - Consumers who gave consent for the processing of their personal data shall have
|
| /Zephyr-Core-3.7.0/tests/net/ptp/clock/src/ |
| D | main.c | 533 static void test_ptp_clock_get_by_xxx(const char *who) in test_ptp_clock_get_by_xxx() argument
539 zassert_not_null(clk_by_index, "PTP 0 not found (%s)", who); in test_ptp_clock_get_by_xxx()
540 zassert_equal(clk0, clk_by_index, "Invalid PTP clock 0 (%s)", who); in test_ptp_clock_get_by_xxx()
546 zassert_not_equal(ret, 0, "ptp_clock_get() failed in %s mode", who); in test_ptp_clock_get_by_xxx()
|
| /Zephyr-Core-3.7.0/doc/connectivity/networking/api/ |
| D | net_offload.rst | 35 functionality at the socket API level. With this approach, vendors who provide an
|
| /Zephyr-Core-3.7.0/doc/project/ |
| D | tsc.rst | 119 - The TSC has the right to terminate elected members who become inactive and are
124 - Existing TSC members who were elected before May 2024 shall be re-confirmed
131 representative who misses three consecutive meetings are subject to suspension
136 members who miss three consecutive TSC weekly meetings.
143 Notice of suspension will be sent to representatives who miss three consecutive
152 Members who opt out and then wish to reclaim their seat later will have their
|
| D | modifying_contributions.rst | 37 A developer who intends to cherry-pick and potentially modify patches sent by
45 A developer who intends to force-push to a branch or pull request of
|
| D | working_groups.rst | 19 - Each working group shall have a team of members who are actively involved
40 Each working group may elect a Chair and optionally a Co-Chair who is
|
| D | project_roles.rst | 31 A *Contributor* is a developer who wishes to contribute to the project,
61 Contributors who show dedication and skill are granted the Triage permission
79 A *Collaborator* is a Contributor who is also responsible for the maintenance
115 A *Maintainer* is a Collaborator who is also responsible for knowing,
|
| /Zephyr-Core-3.7.0/boards/st/stm32g081b_eval/ |
| D | stm32g081b_eval.dts | 165 * a prescaler who's output feeds the 'half-bit' divider which is used
196 * a prescaler who's output feeds the 'half-bit' divider which is used
|
| /Zephyr-Core-3.7.0/ |
| D | CODE_OF_CONDUCT.md | 67 Staff](https://zephyrproject.org/staff/) web pages to identify who are the
126 make explicit who the recipients of Code of Conduct incident reports are.
|
| /Zephyr-Core-3.7.0/boards/st/b_g474e_dpow1/ |
| D | b_g474e_dpow1.dts | 159 * a prescaler who's output feeds the 'half-bit' divider which is used
|
| /Zephyr-Core-3.7.0/boards/st/stm32g071b_disco/ |
| D | stm32g071b_disco.dts | 161 * a prescaler who's output feeds the 'half-bit' divider which is used
|
| /Zephyr-Core-3.7.0/drivers/serial/ |
| D | Kconfig.native_posix | 24 option for users who want to use Zephyr's shell.
|
| /Zephyr-Core-3.7.0/subsys/net/ip/ |
| D | Kconfig.debug | 43 to know who/where the packet was freed already. Do not set this, by
|
| /Zephyr-Core-3.7.0/samples/subsys/zbus/priority_boost/ |
| D | README.rst | 12 developer's application. Those who want to avoid priority inversions between message subscribers and
|
| /Zephyr-Core-3.7.0/boards/96boards/carbon/doc/ |
| D | nrf51822.rst | 129 who are experienced in electronics rework can remove a resistor (R22)
|
| /Zephyr-Core-3.7.0/doc/kernel/services/data_passing/ |
| D | fifos.rst | 61 them one at a time, and can be used to guarantee that anyone who removes
|
| /Zephyr-Core-3.7.0/doc/security/ |
| D | secure-coding.rst | 137 The Zephyr project must have at least one primary developer who knows
187 A "primary developer" in a project is anyone who is familiar with the
|
| D | reporting.rst | 212 platinum members, and volunteers who do work on triage from other
|
| /Zephyr-Core-3.7.0/doc/safety/ |
| D | safety_overview.rst | 12 This overview is provided for people who are interested in the functional safety development part
13 of the Zephyr RTOS and project members who want to contribute to the safety aspects of the
|
| /Zephyr-Core-3.7.0/boards/nxp/imx93_evk/doc/ |
| D | index.rst | 145 Since this board doesn't have a DSP, an alternative for people who might be interested
|
| /Zephyr-Core-3.7.0/boards/ti/cc3220sf_launchxl/doc/ |
| D | index.rst | 89 The following instructions are geared towards Linux developers who
|
| /Zephyr-Core-3.7.0/doc/contribute/ |
| D | guidelines.rst | 123 person who certified (a), (b) or (c) and I have not modified
341 We need to know who you are, and how to contact you. To add this
721 the respective maintainer who is responsible for the affected code.
946 those who asked for the changes
|
| /Zephyr-Core-3.7.0/cmake/modules/ |
| D | kconfig.cmake | 439 # Remove those who might have changed compared to earlier runs, if they no longer appears.
|
| /Zephyr-Core-3.7.0/boards/ti/cc3235sf_launchxl/doc/ |
| D | index.rst | 89 The following instructions are geared towards Linux developers who
|
12
