Deprecate NET_SOCKETS_POSIX_NAMES option

doc/connectivity/networking/api/sockets.rst

@@ -22,7 +22,7 @@ compatible API implementation for Zephyr:
 * Is namespaced by default, to avoid name conflicts with well-known
   names like ``close()``, which may be part of libc or other POSIX
   compatibility libraries.
-  If enabled by :kconfig:option:`CONFIG_NET_SOCKETS_POSIX_NAMES`, it will also
+  If enabled by :kconfig:option:`CONFIG_POSIX_API`, it will also
   expose native POSIX names.
 
 BSD Sockets compatible API is enabled using :kconfig:option:`CONFIG_NET_SOCKETS`
@@ -35,7 +35,7 @@ config option and implements the following operations: ``socket()``, ``close()``
 Based on the namespacing requirements above, these operations are by
 default exposed as functions with ``zsock_`` prefix, e.g.
 :c:func:`zsock_socket` and :c:func:`zsock_close`. If the config option
-:kconfig:option:`CONFIG_NET_SOCKETS_POSIX_NAMES` is defined, all the functions
+:kconfig:option:`CONFIG_POSIX_API` is defined, all the functions
 will be also exposed as aliases without the prefix. This includes the
 functions like ``close()`` and ``fcntl()`` (which may conflict with
 functions in libc or other libraries, for example, with the filesystem

doc/releases/migration-guide-3.7.rst

@@ -178,6 +178,18 @@ Bluetooth Classic
 Networking
 **********
 
+* Deprecate the :kconfig:option:`CONFIG_NET_SOCKETS_POSIX_NAMES` option. It is a legacy option
+  and was used to allow user to call BSD socket API while not enabling POSIX API.
+  This could cause complications when building applications that wanted to enable the
+  :kconfig:option:`CONFIG_POSIX_API` option. This means that if the application wants to use
+  normal BSD socket interface, then it needs to enable :kconfig:option:`CONFIG_POSIX_API`.
+  If the application does not want or is not able to enable that option, then the socket API
+  calls need to be prefixed by a ``zsock_`` string.
+  All the sample applications that use BSD socket interface are changed to enable
+  :kconfig:option:`CONFIG_POSIX_API`. Internally the network stack will not enable POSIX API
+  option which means that various network libraries that use sockets, are converted to
+  use the ``zsock_*`` API calls. (:github:`69950`)
+
 * The zperf zperf_results struct is changed to support 64 bits transferred bytes (total_len)
   and test duration (time_in_us and client_time_in_us), instead of 32 bits. This will make
   the long-duration zperf test show with correct throughput result.

doc/services/portability/posix/kconfig/index.rst

@@ -24,7 +24,6 @@ implementation of the POSIX API.
 * :kconfig:option:`CONFIG_NET_SOCKETPAIR`
 * :kconfig:option:`CONFIG_NET_SOCKETS`
 * :kconfig:option:`CONFIG_NET_SOCKETS_POLL_MAX`
-* :kconfig:option:`CONFIG_NET_SOCKETS_POSIX_NAMES`
 * :kconfig:option:`CONFIG_POSIX_API`
 * :kconfig:option:`CONFIG_POSIX_CLOCK`
 * :kconfig:option:`CONFIG_POSIX_FS`