Revert "doc: posix: mark posix signals supported with undefined behaviour"

This reverts commit b10f1ca.

PR zephyrproject-rtos#73978 introduced a regression.
Unfortunately this PR cannot be reverted without reverting also
Let's revert both PRs to stabilize main again towards the 3.7 release.

For more details on the issue see
zephyrproject-rtos#75205

(cherry picked from commit b2ca594)

Original-Signed-off-by: Alberto Escolar Piedras <[email protected]>
GitOrigin-RevId: b2ca594
Change-Id: I41a3ff34b14a511d5cfaa241b523310b5eda93d8
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/zephyr/+/5678569
Reviewed-by: Fabio Baltieri <[email protected]>
Commit-Queue: Fabio Baltieri <[email protected]>
Tested-by: ChromeOS Prod (Robot) <[email protected]>

Author: aescolar

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

@@ -50,8 +50,8 @@ The *Minimal Realtime System Profile* (PSE51) includes all of the
 
     :ref:`POSIX_C_LANG_JUMP <posix_option_group_c_lang_jump>`, yes,
     :ref:`POSIX_C_LANG_SUPPORT <posix_option_group_c_lang_support>`, yes,
-    :ref:`POSIX_DEVICE_IO <posix_option_group_device_io>`,yes, :kconfig:option:`CONFIG_POSIX_DEVICE_IO`
-    :ref:`POSIX_SIGNALS <posix_option_group_signals>`, yes, :kconfig:option:`CONFIG_POSIX_SIGNALS` :ref:`†<posix_undefined_behaviour>`
+    :ref:`POSIX_DEVICE_IO <posix_option_group_device_io>`, yes, :kconfig:option:`CONFIG_POSIX_DEVICE_IO`
+    :ref:`POSIX_SIGNALS <posix_option_group_signals>`,, :kconfig:option:`CONFIG_POSIX_SIGNALS`
     :ref:`POSIX_SINGLE_PROCESS <posix_option_group_single_process>`, yes, :kconfig:option:`CONFIG_POSIX_SINGLE_PROCESS`
     :ref:`XSI_THREADS_EXT <posix_option_group_xsi_threads_ext>`, yes, :kconfig:option:`CONFIG_XSI_THREADS_EXT`
 

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

@@ -244,34 +244,26 @@ POSIX_SIGNALS
 Signal services are a basic mechanism within POSIX-based systems and are
 required for error and event handling.
 
-.. note::
-   As processes are not yet supported in Zephyr, the ISO C functions ``abort()``, ``signal()``,
-   and ``raise()``, as well as the other POSIX functions listed below, may exhibit undefined
-   behaviour. The POSIX functions ``kill()``, ``pause()``, ``sigaction()``, ``sigpending()``,
-   ``sigsuspend()``, and ``sigwait()`` are implemented to ensure that conformant applications can
-   link, but they are expected to fail, setting errno to ``ENOSYS``
-   :ref:`†<posix_undefined_behaviour>`.
-
 .. csv-table:: POSIX_SIGNALS
    :header: API, Supported
    :widths: 50,10
 
-    abort(),yes :ref:`†<posix_undefined_behaviour>`
-    alarm(),yes :ref:`†<posix_undefined_behaviour>`
-    kill(),yes :ref:`†<posix_undefined_behaviour>`
-    pause(),yes :ref:`†<posix_undefined_behaviour>`
-    raise(),yes :ref:`†<posix_undefined_behaviour>`
-    sigaction(),yes :ref:`†<posix_undefined_behaviour>`
+    abort(),yes
+    alarm(),
+    kill(),
+    pause(),
+    raise(),
+    sigaction(),
     sigaddset(),yes
     sigdelset(),yes
     sigemptyset(),yes
     sigfillset(),yes
     sigismember(),yes
-    signal(),yes :ref:`†<posix_undefined_behaviour>`
-    sigpending(),yes :ref:`†<posix_undefined_behaviour>`
+    signal(),
+    sigpending(),
     sigprocmask(),yes
-    sigsuspend(),yes :ref:`†<posix_undefined_behaviour>`
-    sigwait(),yes :ref:`†<posix_undefined_behaviour>`
+    sigsuspend(),
+    sigwait(),
     strsignal(),yes
 
 .. _posix_option_group_device_io: