Searched refs:success (Results 51 – 65 of 65) sorted by relevance
123
| /Zephyr-latest/doc/_doxygen/ |
| D | doxygen-awesome.css | 2400 …-wrapper:hover doxygen-awesome-fragment-copy-button, doxygen-awesome-fragment-copy-button.success {
2404 doxygen-awesome-fragment-copy-button:hover, doxygen-awesome-fragment-copy-button.success {
2408 doxygen-awesome-fragment-copy-button:active:not([class~=success]) svg {
2418 doxygen-awesome-fragment-copy-button.success svg {
2422 doxygen-awesome-fragment-copy-button.success {
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | mcumgr_callbacks.rst | 262 /* All handlers returned success codes */
|
| /Zephyr-latest/samples/net/sockets/dumb_http_server_mt/src/ |
| D | response_100k.html.bin | 35 …ations and image processing. The most recent example of the technology’s success is the successful…
|
| /Zephyr-latest/scripts/ |
| D | spelling.txt | 1504 sucess||success
1619 usccess||success
|
| /Zephyr-latest/tests/bluetooth/tester/src/ |
| D | btp_mesh.c | 338 const struct bt_mesh_blob_xfer *xfer, bool success) in blob_cli_end() argument
340 if (success) { in blob_cli_end()
403 const struct bt_mesh_dfu_img *img, bool success) in dfu_end() argument
405 if (!success) { in dfu_end()
|
| /Zephyr-latest/boards/intel/adsp/doc/ |
| D | chromebooks_adsp.rst | 395 it reports success, the application begins running immediately and its
|
| /Zephyr-latest/doc/kernel/drivers/ |
| D | index.rst | 428 check, 0 should be returned on success and a POSIX :file:`errno.h` code
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-2.7.rst | 657 * Fixed a bug, where Register failures were reported as success to the
1393 * :github:`37652` - bluetooth: tests/bluetooth/bsim_bt/bsim_test_advx reported success but still re…
1702 * :github:`36037` - bt_init returning success when Bluetooth initialization does not get finalized.
1867 * :github:`31499` - lwm2m : Add visibility into observer notification success/fail
|
| D | release-notes-3.2.rst | 1437 * Issue with :c:func:`img_mgmt_dfu_stopped` being wrongly called on success
1439 * Issue with MCUMGR img_mgmt image erase wrongly returning success during an
1989 * :github:`49498` - net: lib: coap: update method_from_code() to report success/failure
2498 * :github:`44579` - MCC: Discovery cannot complete with success
|
| D | release-notes-1.14.rst | 1239 …4840` - settings: settings_save_one() doesn't always seem to store data, even if it returns success
1305 * :github:`14504` - mempool can return success if no memory was available
1675 * :github:`12650` - drivers: wifi: simplelink: socket() always returns fd of zero on success
|
| D | release-notes-3.4.rst | 192 registration function now returns a value which is 0 for success or a
|
| D | release-notes-3.6.rst | 992 an unknown error. It now returns success.
|
| D | release-notes-3.1.rst | 1216 - :github:`44579` - MCC: Discovery cannot complete with success
|
| /Zephyr-latest/subsys/bluetooth/host/ |
| D | hci_core.c | 431 __maybe_unused bool success = process_pending_cmd(HCI_CMD_TIMEOUT); in bt_hci_cmd_send_sync() local
433 BT_ASSERT_MSG(success, "command opcode 0x%04x timeout", opcode); in bt_hci_cmd_send_sync()
|
| /Zephyr-latest/doc/contribute/ |
| D | guidelines.rst | 533 GitHub PR page, below the review status. Depending on the success or failure
|
123
