Searched refs:resolving (Results 1 – 11 of 11) sorted by relevance
307 uint8_t resolving; member398 priv->resolving = 1U; in report_discovery_results()553 priv->resolving = 0U; in bt_hci_remote_name_request_complete()605 if (priv->resolving) { in bt_hci_remote_name_request_complete()1001 if (!priv->resolving) { in bt_br_discovery_stop()
7 enabling/disabling features, and issuing commands like ping or DNS resolving.
125 or DNS resolving. The net-shell is useful when developing network software.
1117 :ref:`resolving your manifest <west-manifest-resolve>` to see the final results1253 :file:`zephyr/west.yml` entirely when resolving imports. West always uses the1312 resolving imports.1876 The ultimate outcomes of resolving manifest imports are:
273 files, resolving the results into a single logical manifest.
625 feature, which eliminates priorities and collision resolving in the
657 * Fixed DNS resolving by ignoring incoming queries while we are resolving a name.1068 * :github:`27931` - Address resolving when eswifi is used causes MPU FAULT1069 * :github:`27929` - Address resolving when eswifi is used causes MPU FAULT
918 * :github:`21970` - net: dns: mDNS resolving fails when responder is also enabled
1194 * :github:`23226` - Bluetooth: host: Peer not resolved when host resolving is used
530 * :github:`18732` - net: mDNS name resolving issue between 2 Zephyr nodes
620 * Added resolving literal IP addresses even when DNS is disabled.
