michaelh/zephyr
1
0
Fork 0
Code Releases Activity

global: Remove leading/trailing blank lines in files

Browse source 
Remove leading/trailing blank lines in .c, .h, .py, .rst, .yml, and
.yaml files.

Will avoid failures with the new CI test in
https://github.com/zephyrproject-rtos/ci-tools/pull/112, though it only
checks changed files.

Move the 'target-notes' target in boards/xtensa/odroid_go/doc/index.rst
to get rid of the trailing blank line there. It was probably misplaced.

Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
This commit is contained in:
Ulf Magnusson 2019-11-18 10:56:50 +01:00 • committed by Ioannis Glaropoulos
commit 984bfae831
253 changed files with 2 additions and 303 deletions
Download patch file Download diff file Expand all files Collapse all files

1
README.rst
View file

@ -1,4 +1,3 @@
.. raw:: html .. raw:: html
<a href="https://www.zephyrproject.org"> <a href="https://www.zephyrproject.org">

1
arch/arc/core/irq_offload.c
View file

@ -34,4 +34,3 @@ void arch_irq_offload(irq_offload_routine_t routine, void *parameter)
irq_unlock(key); irq_unlock(key);
} }

1
arch/arc/core/vector_table.c
View file

@ -64,4 +64,3 @@ struct vector_table _VectorTable Z_GENERIC_SECTION(.exc_vector_table) = {
0, 0,
0 0
}; };

1
arch/nios2/core/irq_offload.c
View file

@ -41,4 +41,3 @@ void arch_irq_offload(irq_offload_routine_t routine, void *parameter)
irq_unlock(key); irq_unlock(key);
} }

1
arch/posix/core/fatal.c
View file

@ -20,4 +20,3 @@ FUNC_NORETURN void arch_system_halt(unsigned int reason)
posix_print_error_and_exit("Exiting due to fatal error\n"); posix_print_error_and_exit("Exiting due to fatal error\n");
CODE_UNREACHABLE; /* LCOV_EXCL_LINE */ CODE_UNREACHABLE; /* LCOV_EXCL_LINE */
} }

1
boards/arc/hsdk/doc/index.rst
View file

@ -479,4 +479,3 @@ References
.. _Digilent Pmod Modules: http://store.digilentinc.com/pmod-modules .. _Digilent Pmod Modules: http://store.digilentinc.com/pmod-modules
.. _Putty website: http://www.putty.org .. _Putty website: http://www.putty.org

1
boards/arm/bbc_microbit/doc/index.rst
View file

@ -103,4 +103,3 @@ References
.. target-notes:: .. target-notes::
.. _microbit website: http://www.microbit.org/ .. _microbit website: http://www.microbit.org/

1
boards/arm/bl652_dvk/doc/bl652_dvk.rst
View file

@ -270,4 +270,3 @@ References
.. target-notes:: .. target-notes::
.. _BL652 Module Website: https://connectivity.lairdtech.com/wireless-modules/bluetooth-modules/bluetooth-5-modules/bl652-series-bluetooth-v5-nfc .. _BL652 Module Website: https://connectivity.lairdtech.com/wireless-modules/bluetooth-modules/bluetooth-5-modules/bl652-series-bluetooth-v5-nfc

1
boards/arm/bl654_dvk/doc/bl654_dvk.rst
View file

@ -186,4 +186,3 @@ References
.. _BL654 website: https://connectivity.lairdtech.com/wireless-modules/bluetooth-modules/bluetooth-5-modules/bl654-series .. _BL654 website: https://connectivity.lairdtech.com/wireless-modules/bluetooth-modules/bluetooth-5-modules/bl654-series
.. _J-Link Software and documentation pack: https://www.segger.com/jlink-software.html .. _J-Link Software and documentation pack: https://www.segger.com/jlink-software.html

1
boards/arm/decawave_dwm1001_dev/Kconfig.defconfig
View file

@ -40,4 +40,3 @@ config BT_CTLR
default BT default BT
endif # BOARD_DECAWAVE_DWM1001_DEV endif # BOARD_DECAWAVE_DWM1001_DEV

1
boards/arm/decawave_dwm1001_dev/doc/index.rst
View file

@ -56,4 +56,3 @@ References
.. _nRF52832 website: https://www.nordicsemi.com/Products/Low-power-short-range-wireless/nRF52832 .. _nRF52832 website: https://www.nordicsemi.com/Products/Low-power-short-range-wireless/nRF52832
.. _Decawave DWM1001 website: https://www.decawave.com/product/dwm1001-module .. _Decawave DWM1001 website: https://www.decawave.com/product/dwm1001-module
.. _Decawave DWM1001-DEV website: https://www.decawave.com/product/dwm1001-development-board .. _Decawave DWM1001-DEV website: https://www.decawave.com/product/dwm1001-development-board

1
boards/arm/mikroe_mini_m4_for_stm32/doc/mikroe_mini_m4_for_stm32.rst
View file

@ -148,4 +148,3 @@ You can debug an application in the usual way. Here is an example for the
https://www.st.com/resource/en/datasheet/stm32f415rg.pdf https://www.st.com/resource/en/datasheet/stm32f415rg.pdf
.. _MINI-M4 for STM32 User Manual: .. _MINI-M4 for STM32 User Manual:
https://download.mikroe.com/documents/starter-boards/mini/stm32/f4/mini-m4-stm32-manual-v100.pdf https://download.mikroe.com/documents/starter-boards/mini/stm32/f4/mini-m4-stm32-manual-v100.pdf

1
boards/arm/mimxrt1015_evk/doc/index.rst
View file

@ -196,4 +196,3 @@ see the following message in the terminal:
.. _i.MX RT1015 Reference Manual: .. _i.MX RT1015 Reference Manual:
https://www.nxp.com/docs/en/reference-manual/IMXRT1015RM.pdf https://www.nxp.com/docs/en/reference-manual/IMXRT1015RM.pdf

1
boards/arm/nrf51_pca10031/doc/index.rst
View file

@ -142,4 +142,3 @@ References
.. _nRF51 Dongle website: http://www.nordicsemi.com/eng/Products/nRF51-Dongle .. _nRF51 Dongle website: http://www.nordicsemi.com/eng/Products/nRF51-Dongle
.. _Nordic Semiconductor Infocenter: http://infocenter.nordicsemi.com/ .. _Nordic Semiconductor Infocenter: http://infocenter.nordicsemi.com/

1
boards/arm/nrf52810_pca10040/doc/index.rst
View file

@ -21,4 +21,3 @@ References
.. target-notes:: .. target-notes::
.. _nRF52810 website: https://www.nordicsemi.com/Products/Low-power-short-range-wireless/nRF52810 .. _nRF52810 website: https://www.nordicsemi.com/Products/Low-power-short-range-wireless/nRF52810

1
boards/arm/nrf52811_pca10056/doc/index.rst
View file

@ -21,4 +21,3 @@ References
.. target-notes:: .. target-notes::
.. _nRF52811 website: https://www.nordicsemi.com/Products/Low-power-short-range-wireless/nRF52811 .. _nRF52811 website: https://www.nordicsemi.com/Products/Low-power-short-range-wireless/nRF52811

2
boards/arm/nrf52832_mdk/doc/index.rst
View file

@ -23,5 +23,3 @@ References
.. _nRF52832 website: https://www.nordicsemi.com/Products/Low-power-short-range-wireless/nRF52832 .. _nRF52832 website: https://www.nordicsemi.com/Products/Low-power-short-range-wireless/nRF52832
.. _nRF52832-mdk website: https://wiki.makerdiary.com/nrf52832-mdk .. _nRF52832-mdk website: https://wiki.makerdiary.com/nrf52832-mdk

1
boards/arm/nrf52840_mdk/doc/index.rst
View file

@ -28,4 +28,3 @@ References
.. _nRF52840 website: https://www.nordicsemi.com/Products/Low-power-short-range-wireless/nRF52840 .. _nRF52840 website: https://www.nordicsemi.com/Products/Low-power-short-range-wireless/nRF52840
.. _nRF52840-mdk website: https://wiki.makerdiary.com/nrf52840-mdk .. _nRF52840-mdk website: https://wiki.makerdiary.com/nrf52840-mdk

1
boards/arm/nrf52840_papyr/doc/nrf52840_papyr.rst
View file

@ -192,4 +192,3 @@ References
.. _Nordic Semiconductor Infocenter: http://infocenter.nordicsemi.com/ .. _Nordic Semiconductor Infocenter: http://infocenter.nordicsemi.com/
.. _Black Magic Probe website: https://github.com/blacksphere/blackmagic .. _Black Magic Probe website: https://github.com/blacksphere/blackmagic
.. _Bumpy website: https://docs.electronut.in/bumpy/ .. _Bumpy website: https://docs.electronut.in/bumpy/

1
boards/arm/nrf52_pca20020/doc/index.rst
View file

@ -386,4 +386,3 @@ References
.. _nRF52 DK website: https://www.nordicsemi.com/Software-and-Tools/Development-Kits/Nordic-Thingy-52 .. _nRF52 DK website: https://www.nordicsemi.com/Software-and-Tools/Development-Kits/Nordic-Thingy-52
.. _Nordic Semiconductor Infocenter: http://infocenter.nordicsemi.com/ .. _Nordic Semiconductor Infocenter: http://infocenter.nordicsemi.com/

1
boards/arm/nrf52_vbluno52/doc/index.rst
View file

@ -105,4 +105,3 @@ components on the VBLUno52 board:
* :ref:`button-sample` * :ref:`button-sample`
* :ref:`bluetooth-beacon-sample` * :ref:`bluetooth-beacon-sample`
* :ref:`peripheral_hr` * :ref:`peripheral_hr`

1
boards/arm/nucleo_f756zg/doc/index.rst
View file

@ -218,4 +218,3 @@ You can debug an application in the usual way. Here is an example for the
.. _STM32F756 reference manual: .. _STM32F756 reference manual:
https://www.st.com/resource/en/reference_manual/dm00124865.pdf https://www.st.com/resource/en/reference_manual/dm00124865.pdf

1
boards/arm/olimex_stm32_e407/doc/index.rst
View file

@ -380,4 +380,3 @@ way. Here is an example for the :ref:`hello_world` application.
.. _ST STM32F407ZG Datasheet: .. _ST STM32F407ZG Datasheet:
http://www.st.com/resource/en/reference_manual/dm00031020.pdf http://www.st.com/resource/en/reference_manual/dm00031020.pdf

1
boards/arm/olimex_stm32_e407/pinmux.c
View file

@ -63,4 +63,3 @@ static int pinmux_stm32_init(struct device *port)
SYS_INIT(pinmux_stm32_init, PRE_KERNEL_1, SYS_INIT(pinmux_stm32_init, PRE_KERNEL_1,
CONFIG_PINMUX_STM32_DEVICE_INITIALIZATION_PRIORITY); CONFIG_PINMUX_STM32_DEVICE_INITIALIZATION_PRIORITY);

1
boards/arm/olimex_stm32_h407/doc/index.rst
View file

@ -377,4 +377,3 @@ way. Here is an example for the :ref:`hello_world` application.
.. _ST STM32F407ZG Datasheet: .. _ST STM32F407ZG Datasheet:
http://www.st.com/resource/en/reference_manual/dm00031020.pdf http://www.st.com/resource/en/reference_manual/dm00031020.pdf

1
boards/arm/olimex_stm32_h407/pinmux.c
View file

@ -43,4 +43,3 @@ static int pinmux_stm32_init(struct device *port)
SYS_INIT(pinmux_stm32_init, PRE_KERNEL_1, SYS_INIT(pinmux_stm32_init, PRE_KERNEL_1,
CONFIG_PINMUX_STM32_DEVICE_INITIALIZATION_PRIORITY); CONFIG_PINMUX_STM32_DEVICE_INITIALIZATION_PRIORITY);

1
boards/arm/olimex_stm32_p405/doc/index.rst
View file

@ -265,4 +265,3 @@ You can debug an application in the usual way. Here is an example for the
.. _ST STM32F405RG Datasheet: .. _ST STM32F405RG Datasheet:
http://www.st.com/resource/en/reference_manual/dm00031020.pdf http://www.st.com/resource/en/reference_manual/dm00031020.pdf

1
boards/arm/sensortile_box/doc/index.rst
View file

@ -203,4 +203,3 @@ References
.. _DFU-UTIL website: .. _DFU-UTIL website:
http://dfu-util.sourceforge.net/ http://dfu-util.sourceforge.net/

1
boards/arm/steval_fcu001v1/Kconfig.board
View file

@ -6,4 +6,3 @@
config BOARD_STEVAL_FCU001V1 config BOARD_STEVAL_FCU001V1
bool "STM32 Flight Controller Unit" bool "STM32 Flight Controller Unit"
depends on SOC_STM32F401XC depends on SOC_STM32F401XC

1
boards/arm/steval_fcu001v1/doc/index.rst
View file

@ -158,4 +158,3 @@ You can debug an application in the usual way. Here is an example for the
.. _STM32F401 reference manual: .. _STM32F401 reference manual:
http://www.st.com/resource/en/reference_manual/dm00096844.pdf http://www.st.com/resource/en/reference_manual/dm00096844.pdf

1
boards/arm/twr_ke18f/pinmux.c
View file

@ -146,4 +146,3 @@ static int twr_ke18f_pinmux_init(struct device *dev)
} }
SYS_INIT(twr_ke18f_pinmux_init, PRE_KERNEL_1, CONFIG_PINMUX_INIT_PRIORITY); SYS_INIT(twr_ke18f_pinmux_init, PRE_KERNEL_1, CONFIG_PINMUX_INIT_PRIORITY);

1
boards/posix/native_posix/cmdline_common.h
View file

@ -83,4 +83,3 @@ void cmd_print_switches_help(struct args_struct_t args_struct[]);
#endif #endif
#endif /* _CMDLINE_COMMON_H */ #endif /* _CMDLINE_COMMON_H */

2
boards/posix/native_posix/doc/index.rst
View file

@ -1,4 +1,3 @@
.. _native_posix: .. _native_posix:
Native POSIX execution (native_posix) Native POSIX execution (native_posix)
@ -657,4 +656,3 @@ these commands::
$ sudo apt-get install pkg-config libfuse-dev:i386 $ sudo apt-get install pkg-config libfuse-dev:i386
$ export PKG_CONFIG_PATH=/usr/lib/i386-linux-gnu/pkgconfig $ export PKG_CONFIG_PATH=/usr/lib/i386-linux-gnu/pkgconfig

1
boards/posix/native_posix/dts_fixup.h
View file

@ -6,4 +6,3 @@
#define DT_FLASH_DEV_NAME DT_INST_0_ZEPHYR_SIM_FLASH_LABEL #define DT_FLASH_DEV_NAME DT_INST_0_ZEPHYR_SIM_FLASH_LABEL
#define DT_UART_0_DEV_NAME DT_ZEPHYR_NATIVE_POSIX_UART_UART_LABEL #define DT_UART_0_DEV_NAME DT_ZEPHYR_NATIVE_POSIX_UART_UART_LABEL

2
boards/posix/native_posix/hw_models_top.c
View file

@ -209,5 +209,3 @@ void hwm_cleanup(void)
hwtimer_cleanup(); hwtimer_cleanup();
hw_irq_ctrl_cleanup(); hw_irq_ctrl_cleanup();
} }

2
boards/posix/native_posix/irq_ctrl.c
View file

@ -269,5 +269,3 @@ void hw_irq_ctrl_timer_triggered(void)
irq_ctrl_timer = NEVER; irq_ctrl_timer = NEVER;
irq_raising_from_hw_now(); irq_raising_from_hw_now();
} }

1
boards/posix/native_posix/sdl_events.h
View file

@ -11,4 +11,3 @@
void sdl_handle_events(void); void sdl_handle_events(void);
#endif /* ZEPHYR_BOARD_POSIX_NATIVE_POSIX_SDL_EVENTS_H */ #endif /* ZEPHYR_BOARD_POSIX_NATIVE_POSIX_SDL_EVENTS_H */

1
boards/posix/nrf52_bsim/doc/index.rst
View file

@ -1,4 +1,3 @@
.. _nrf52_bsim: .. _nrf52_bsim:
NRF52 simulated board (BabbleSim) NRF52 simulated board (BabbleSim)

1
boards/shields/adafruit_2_8_tft_touch_v2/doc/index.rst
View file

@ -65,4 +65,3 @@ References
.. _Adafruit 2.8" TFT Touch Shield v2 website: .. _Adafruit 2.8" TFT Touch Shield v2 website:
https://learn.adafruit.com/adafruit-2-8-tft-touch-shield-v2 https://learn.adafruit.com/adafruit-2-8-tft-touch-shield-v2

1
boards/shields/waveshare_epaper/doc/index.rst
View file

@ -85,4 +85,3 @@ References
.. _Universal e-Paper Raw Panel Driver Shield website: .. _Universal e-Paper Raw Panel Driver Shield website:
https://www.waveshare.com/e-paper-shield.htm https://www.waveshare.com/e-paper-shield.htm

1
boards/x86/acrn/acrn.yaml
View file

@ -5,4 +5,3 @@ arch: x86
toolchain: toolchain:
- zephyr - zephyr
ram: 8192 ram: 8192

6
boards/xtensa/odroid_go/doc/index.rst
View file

@ -164,10 +164,8 @@ your terminal:
References References
********** **********
.. target-notes::
.. [1] https://wiki.odroid.com/odroid_go/odroid_go .. [1] https://wiki.odroid.com/odroid_go/odroid_go
.. _`toolchain`: https://docs.espressif.com/projects/esp-idf/en/latest/get-started/index.html#get-started-setup-toolchain .. _`toolchain`: https://docs.espressif.com/projects/esp-idf/en/latest/get-started/index.html#get-started-setup-toolchain
.. _`SDK`: https://docs.espressif.com/projects/esp-idf/en/latest/get-started/index.html#get-started-get-esp-idf .. _`SDK`: https://docs.espressif.com/projects/esp-idf/en/latest/get-started/index.html#get-started-get-esp-idf
.. target-notes::

1
boards/xtensa/xt-sim/doc/index.rst
View file

@ -180,4 +180,3 @@ References
********** **********
.. _Xtensa tools: https://ip.cadence.com/support/sdk-evaluation-request .. _Xtensa tools: https://ip.cadence.com/support/sdk-evaluation-request

1
doc/development_process/api_lifecycle.rst
View file

@ -134,4 +134,3 @@ the release notes, mailing lists, Github issues and pull-requests.
If it's not OK to remove the API, the maintainers will continue to support If it's not OK to remove the API, the maintainers will continue to support
migration and update the roadmap with the aim to remove the API in the next migration and update the roadmap with the aim to remove the API in the next
release. release.

2
doc/development_process/index.rst
View file

@ -27,5 +27,3 @@ Terminology
- upstream: A parent branch the source code is based on. This is the branch you - upstream: A parent branch the source code is based on. This is the branch you
pull from and push to, basically your upstream. pull from and push to, basically your upstream.
- LTS: Long Term Support - LTS: Long Term Support

1
doc/development_process/issues.rst
View file

@ -12,4 +12,3 @@ identifiers.
At any time it should be possible to establish the origin of a change and the At any time it should be possible to establish the origin of a change and the
reason behind it by following the references in the code. reason behind it by following the references in the code.

1
doc/guides/bluetooth/bluetooth-qual.rst
View file

@ -78,4 +78,3 @@ the following documents:
sm-pics.rst sm-pics.rst
rfcomm-pics.rst rfcomm-pics.rst
mesh-pics.rst mesh-pics.rst

1
doc/guides/bluetooth/gap-pics.rst
View file

@ -792,4 +792,3 @@ TSPC_GAP_45_1 False (*) Simultaneous BR/EDR and LE Transports - BR/EDR
TSPC_GAP_45_2 False (*) Simultaneous BR/EDR and LE Transports - BR/EDR TSPC_GAP_45_2 False (*) Simultaneous BR/EDR and LE Transports - BR/EDR
Master to the same device (C.1) Master to the same device (C.1)
============== ============== ======================================= ============== ============== =======================================

1
doc/guides/bluetooth/gatt-pics.rst
View file

@ -281,4 +281,3 @@ Parameter Name Selected Description
TSPC_GATT_8_1 False (*) Support for Multiple ATT bearers from same TSPC_GATT_8_1 False (*) Support for Multiple ATT bearers from same
device (C.1) device (C.1)
============== =========== ============================================ ============== =========== ============================================

1
doc/guides/bluetooth/l2cap-pics.rst
View file

@ -143,4 +143,3 @@ TSPC_L2CAP_3_15 False (*) Negotiate and support service type
TSPC_L2CAP_3_16 True Support Multiple Simultaneous LE Data TSPC_L2CAP_3_16 True Support Multiple Simultaneous LE Data
Channels Channels
================ =========== ======================================= ================ =========== =======================================

3
doc/guides/bluetooth/overview.rst
View file

@ -93,6 +93,3 @@ Bluetooth stack.
* Local controller support as a virtual HCI driver * Local controller support as a virtual HCI driver
* Verified with multiple popular controllers * Verified with multiple popular controllers

1
doc/guides/c_library.rst
View file

@ -74,4 +74,3 @@ library included with Zephyr:
- toupper() - toupper()
- vsnprintf() - vsnprintf()
- vsprintf() - vsprintf()

1
doc/guides/coverage.rst
View file

@ -141,4 +141,3 @@ which will produce ``sanity-out/coverage/index.html`` with the report.
.. _gcov: .. _gcov:
https://gcc.gnu.org/onlinedocs/gcc/Gcov.html https://gcc.gnu.org/onlinedocs/gcc/Gcov.html

1
doc/guides/modules.rst
View file

@ -1,4 +1,3 @@
.. _modules: .. _modules:
Modules (External projects) Modules (External projects)

2
doc/guides/portability/posix.rst
View file

@ -1,5 +1,3 @@
POSIX Support POSIX Support
############# #############

1
doc/guides/porting/arch.rst
View file

@ -613,4 +613,3 @@ Miscellaneous Architecture APIs
.. doxygengroup:: arch-misc .. doxygengroup:: arch-misc
:project: Zephyr :project: Zephyr

1
doc/guides/test/sanitycheck.rst
View file

@ -1,4 +1,3 @@
.. _sanitycheck_script: .. _sanitycheck_script:
Sanity Tests Sanity Tests

1
doc/guides/tools/nordic_segger.rst
View file

@ -241,4 +241,3 @@ References
.. _blacklist Segger devices by editing udev rules: http://www.at91.com/linux4sam/bin/view/Linux4SAM/SoftwareTools#Device_or_resource_busy_dev_ttyA .. _blacklist Segger devices by editing udev rules: http://www.at91.com/linux4sam/bin/view/Linux4SAM/SoftwareTools#Device_or_resource_busy_dev_ttyA
.. _J-Link Software and documentation pack: https://www.segger.com/jlink-software.html .. _J-Link Software and documentation pack: https://www.segger.com/jlink-software.html

3
doc/guides/tracing/index.rst
View file

@ -278,6 +278,3 @@ Locking may not be needed if multiple independent channels are available.
E.g. native_posix or board with multi-channel DMA. Lock-free. E.g. native_posix or board with multi-channel DMA. Lock-free.
``emit(a ## b ## c, thread_id);`` ``emit(a ## b ## c, thread_id);``

1
doc/guides/west/release-notes.rst
View file

@ -170,4 +170,3 @@ historical interest only.
.. _west v0.5.x documentation: .. _west v0.5.x documentation:
https://docs.zephyrproject.org/1.14.0/guides/west/index.html https://docs.zephyrproject.org/1.14.0/guides/west/index.html

1
doc/guides/west/west-not-found.rst
View file

@ -13,4 +13,3 @@ West APIs
The west APIs are not documented since either west was missing or the zephyr The west APIs are not documented since either west was missing or the zephyr
repository was not initialized using west during the documentation build. repository was not initialized using west during the documentation build.

1
doc/guides/west/zephyr-cmds.rst
View file

@ -36,4 +36,3 @@ flag::
Additional help about the formatting options can be found by running:: Additional help about the formatting options can be found by running::
west boards -h west boards -h

2
doc/reference/bluetooth/connection_mgmt.rst
View file

@ -29,5 +29,3 @@ API Reference
.. doxygengroup:: bt_conn .. doxygengroup:: bt_conn
:project: Zephyr :project: Zephyr

1
doc/reference/bluetooth/gatt.rst
View file

@ -109,4 +109,3 @@ GATT Client
.. doxygengroup:: bt_gatt_client .. doxygengroup:: bt_gatt_client
:project: Zephyr :project: Zephyr

1
doc/reference/index.rst
View file

@ -23,4 +23,3 @@ API Reference
usb/index.rst usb/index.rst
usermode/index.rst usermode/index.rst
runtime_conf/index.rst runtime_conf/index.rst

1
doc/reference/kernel/data_passing/stacks.rst
View file

@ -141,4 +141,3 @@ API Reference
.. doxygengroup:: stack_apis .. doxygengroup:: stack_apis
:project: Zephyr :project: Zephyr

1
doc/reference/kernel/memory/pools.rst
View file

@ -205,4 +205,3 @@ API Reference
.. doxygengroup:: mem_pool_apis .. doxygengroup:: mem_pool_apis
:project: Zephyr :project: Zephyr

1
doc/reference/kernel/other/atomic.rst
View file

@ -118,4 +118,3 @@ API Reference
.. doxygengroup:: atomic_apis .. doxygengroup:: atomic_apis
:project: Zephyr :project: Zephyr

1
doc/reference/kernel/other/fatal.rst
View file

@ -260,4 +260,3 @@ API Reference
.. doxygengroup:: fatal_apis .. doxygengroup:: fatal_apis
:project: Zephyr :project: Zephyr

1
doc/reference/kernel/other/float.rst
View file

@ -250,4 +250,3 @@ API Reference
.. doxygengroup:: float_apis .. doxygengroup:: float_apis
:project: Zephyr :project: Zephyr

1
doc/reference/kernel/scheduling/index.rst
View file

@ -265,4 +265,3 @@ for a kernel object, such as a mutex.
Use preemptive threads to give priority to time-sensitive processing Use preemptive threads to give priority to time-sensitive processing
over less time-sensitive processing. over less time-sensitive processing.

1
doc/reference/kernel/synchronization/mutexes.rst
View file

@ -166,4 +166,3 @@ API Reference
.. doxygengroup:: mutex_apis .. doxygengroup:: mutex_apis
:project: Zephyr :project: Zephyr

1
doc/reference/kernel/synchronization/semaphores.rst
View file

@ -130,4 +130,3 @@ API Reference
.. doxygengroup:: semaphore_apis .. doxygengroup:: semaphore_apis
:project: Zephyr :project: Zephyr

1
doc/reference/kernel/threads/system_threads.rst
View file

@ -1,4 +1,3 @@
.. _system_threads_v2: .. _system_threads_v2:
System Threads System Threads

1
doc/reference/kernel/threads/workqueue.rst
View file

@ -1,4 +1,3 @@
.. _workqueues_v2: .. _workqueues_v2:
Workqueue Threads Workqueue Threads

1
doc/reference/logging/index.rst
View file

@ -556,4 +556,3 @@ Logger output formatting
.. doxygengroup:: log_output .. doxygengroup:: log_output
:project: Zephyr :project: Zephyr

1
doc/reference/networking/can_api.rst
View file

@ -332,4 +332,3 @@ API Reference
.. doxygengroup:: can_interface .. doxygengroup:: can_interface
:project: Zephyr :project: Zephyr

1
doc/reference/networking/protocols.rst
View file

@ -10,4 +10,3 @@ Protocols
coap coap
lwm2m lwm2m
mqtt mqtt

1
doc/reference/peripherals/i2c_eeprom_slave.rst
View file

@ -11,4 +11,3 @@ API Reference
.. doxygengroup:: i2c_eeprom_slave_api .. doxygengroup:: i2c_eeprom_slave_api
:project: Zephyr :project: Zephyr

2
doc/reference/random/index.rst
View file

@ -97,5 +97,3 @@ API Reference
.. doxygengroup:: random_api .. doxygengroup:: random_api
:project: Zephyr :project: Zephyr

1
doc/reference/storage/flash_map/flash_map.rst
View file

@ -34,4 +34,3 @@ flash_area API
.. doxygengroup:: flash_area_api .. doxygengroup:: flash_area_api
:project: Zephyr :project: Zephyr

1
doc/reference/usermode/mpu_stack_objects.rst
View file

@ -62,4 +62,3 @@ logically OR regions to determine enforcement policy.
Size and alignment constraints may result in stack allocations being larger Size and alignment constraints may result in stack allocations being larger
than the requested size. Region priority mechanisms may result in than the requested size. Region priority mechanisms may result in
some added complexity when implementing stack guards. some added complexity when implementing stack guards.

1
doc/reference/usermode/mpu_userspace.rst
View file

@ -23,4 +23,3 @@ passed-in parameters are all validated. The user mode thread is then elevated
to privileged mode, the stack is switched to use the privileged stack, and the to privileged mode, the stack is switched to use the privileged stack, and the
call is made to the specified kernel API. On return from the kernel API, the call is made to the specified kernel API. On return from the kernel API, the
thread is set back to user mode and the stack is restored to the user stack. thread is set back to user mode and the stack is restored to the user stack.

1
doc/reference/usermode/syscalls.rst
View file

@ -355,4 +355,3 @@ Functions for invoking system calls are defined in
* :c:func:`_arch_syscall_invoke4` * :c:func:`_arch_syscall_invoke4`
* :c:func:`_arch_syscall_invoke5` * :c:func:`_arch_syscall_invoke5`
* :c:func:`_arch_syscall_invoke6` * :c:func:`_arch_syscall_invoke6`

1
doc/releases/release-notes-1.11.rst
View file

@ -502,4 +502,3 @@ release:
* :github:`6471` - tests/crypto/aes results in Assertion failure on esp32 * :github:`6471` - tests/crypto/aes results in Assertion failure on esp32
* :github:`6472` - tests/crypto/sha256 results in Assertion failure on esp32 * :github:`6472` - tests/crypto/sha256 results in Assertion failure on esp32
* :github:`6505` - Userspace support: stack corruption for ARC em7d v2.3 * :github:`6505` - Userspace support: stack corruption for ARC em7d v2.3

2
doc/releases/release-notes-1.6.rst
View file

@ -370,5 +370,3 @@ Known Issues
* :jira:`ZEP-1405` - function l2cap_br_conn_req in /subsys/bluetooth/host/l2cap_br.c * :jira:`ZEP-1405` - function l2cap_br_conn_req in /subsys/bluetooth/host/l2cap_br.c
references uninitialized pointer references uninitialized pointer

2
doc/releases/release-notes-1.7.rst
View file

@ -454,5 +454,3 @@ JIRA Related Items
* :jira:`ZEP-1877` - samples/net: the coaps_server sample app runs failed on Arduino 101 * :jira:`ZEP-1877` - samples/net: the coaps_server sample app runs failed on Arduino 101
* :jira:`ZEP-1883` - Enabling Console on ARC Genuino 101 * :jira:`ZEP-1883` - Enabling Console on ARC Genuino 101
* :jira:`ZEP-1890` - Bluetooth IPSP sample: Too small user data size * :jira:`ZEP-1890` - Bluetooth IPSP sample: Too small user data size

1
doc/security/security-citations.rst
View file

@ -47,4 +47,3 @@ Security Document Citations
.. [CIIBPB] Core Infrastructure Initiative Best Practices Badge. [Online]. .. [CIIBPB] Core Infrastructure Initiative Best Practices Badge. [Online].
Available: https://github.com/linuxfoundation/cii-best-practices-badge Available: https://github.com/linuxfoundation/cii-best-practices-badge

1
drivers/console/native_posix_console.c
View file

@ -269,4 +269,3 @@ static int native_posix_console_init(struct device *arg)
SYS_INIT(native_posix_console_init, PRE_KERNEL_1, SYS_INIT(native_posix_console_init, PRE_KERNEL_1,
CONFIG_NATIVE_POSIX_CONSOLE_INIT_PRIORITY); CONFIG_NATIVE_POSIX_CONSOLE_INIT_PRIORITY);

3
drivers/console/xtensa_sim_console.c
View file

@ -82,6 +82,3 @@ SYS_INIT(xt_sim_console_init,
POST_KERNEL, POST_KERNEL,
#endif #endif
CONFIG_XTENSA_CONSOLE_INIT_PRIORITY); CONFIG_XTENSA_CONSOLE_INIT_PRIORITY);

1
drivers/display/display_dummy.c
View file

@ -111,4 +111,3 @@ DEVICE_AND_API_INIT(dummy_display, CONFIG_DUMMY_DISPLAY_DEV_NAME,
&dummy_display_init, &dummy_display_data, NULL, &dummy_display_init, &dummy_display_data, NULL,
APPLICATION, CONFIG_APPLICATION_INIT_PRIORITY, APPLICATION, CONFIG_APPLICATION_INIT_PRIORITY,
&dummy_display_api); &dummy_display_api);

1
drivers/dma/dma_handlers.c
View file

@ -24,4 +24,3 @@ static inline int z_vrfy_dma_stop(struct device *dev, u32_t channel)
return z_impl_dma_stop((struct device *)dev, channel); return z_impl_dma_stop((struct device *)dev, channel);
} }
#include <syscalls/dma_stop_mrsh.c> #include <syscalls/dma_stop_mrsh.c>

1
drivers/flash/soc_flash_mcux.c
View file

@ -159,4 +159,3 @@ static int flash_mcux_init(struct device *dev)
DEVICE_AND_API_INIT(flash_mcux, DT_FLASH_DEV_NAME, DEVICE_AND_API_INIT(flash_mcux, DT_FLASH_DEV_NAME,
flash_mcux_init, &flash_data, NULL, POST_KERNEL, flash_mcux_init, &flash_data, NULL, POST_KERNEL,
CONFIG_KERNEL_INIT_PRIORITY_DEVICE, &flash_mcux_api); CONFIG_KERNEL_INIT_PRIORITY_DEVICE, &flash_mcux_api);

1
drivers/flash/soc_flash_rv32m1.c
View file

@ -165,4 +165,3 @@ static int flash_mcux_init(struct device *dev)
DEVICE_AND_API_INIT(flash_mcux, DT_FLASH_DEV_NAME, DEVICE_AND_API_INIT(flash_mcux, DT_FLASH_DEV_NAME,
flash_mcux_init, &flash_data, NULL, POST_KERNEL, flash_mcux_init, &flash_data, NULL, POST_KERNEL,
CONFIG_KERNEL_INIT_PRIORITY_DEVICE, &flash_mcux_api); CONFIG_KERNEL_INIT_PRIORITY_DEVICE, &flash_mcux_api);

1
drivers/gpio/gpio_ht16k33.c
View file

@ -260,4 +260,3 @@ GPIO_HT16K33_DEVICE(22);
#ifdef DT_INST_23_HOLTEK_HT16K33_KEYSCAN #ifdef DT_INST_23_HOLTEK_HT16K33_KEYSCAN
GPIO_HT16K33_DEVICE(23); GPIO_HT16K33_DEVICE(23);
#endif #endif

1
drivers/interrupt_controller/system_apic.c
View file

@ -100,4 +100,3 @@ void arch_irq_disable(unsigned int irq)
z_loapic_irq_disable(irq - LOAPIC_IRQ_BASE); z_loapic_irq_disable(irq - LOAPIC_IRQ_BASE);
} }
} }

1
drivers/kscan/kscan_mchp_xec.c
View file

@ -405,4 +405,3 @@ static int kscan_xec_init(struct device *dev)
return 0; return 0;
} }

1
drivers/pcie/Kconfig
View file

@ -26,4 +26,3 @@ config PCIE_SHELL
Enable commands for debugging PCI(e) using the built-in shell. Enable commands for debugging PCI(e) using the built-in shell.
endif # PCIE endif # PCIE

1
drivers/pwm/pwm_sifive.c
View file

@ -249,4 +249,3 @@ PWM_SIFIVE_INIT(1);
#ifdef DT_INST_2_SIFIVE_PWM0_LABEL #ifdef DT_INST_2_SIFIVE_PWM0_LABEL
PWM_SIFIVE_INIT(2); PWM_SIFIVE_INIT(2);
#endif /* DT_INST_2_SIFIVE_PWM0_LABEL */ #endif /* DT_INST_2_SIFIVE_PWM0_LABEL */

1
drivers/sensor/bme680/Kconfig
View file

@ -115,4 +115,3 @@ endchoice
endmenu # BME680 Attributes endmenu # BME680 Attributes
endif # BME680 endif # BME680

Some files were not shown because too many files have changed in this diff Show more