Remove the double blank line from source files

Signed-off-by: Xiang Xiao <[email protected]>

Author: xiaoxiang781216

Documentation/applications/nsh/builtin.rst

@@ -169,7 +169,6 @@ that in ``apps/examples/hello/Makefile`` is abstracted below:
       context:
         $(call REGISTER,$(APPNAME),$(PRIORITY),$(STACKSIZE),$(APPNAME)_main)
 
-
 **Other Uses of Built-In Application.** The primary purpose of builtin
 applications is to support command line execution of applications from
 NSH. However, there is one other use of builtin applications that should

Documentation/applications/nsh/commands.rst

@@ -1843,4 +1843,3 @@ Example::
 
 ``ping6`` differs from ``ping`` in that it uses IPv6 addressing.
 
-

Documentation/applications/nsh/config.rst

@@ -398,7 +398,6 @@ CMD                 w/o ``CONFIG_NSH_VARS``               w/``CONFIG_NSH_VARS``
 ``env``             Lists all environment variables       Lists all environment variables (*only*)
 ==================  ===================================   =============================================
 
-
 If Telnet is selected for the NSH console, then we must configure the
 resources used by the Telnet daemon and by the Telnet clients.
 

Documentation/applications/nsh/nsh.rst

@@ -358,4 +358,3 @@ containing the ROMFS file system image.
 NuttShell <#customizingnsh>`__ for additional, more detailed
 information about the NSH start-up script and how to modify it.
 
-

Documentation/components/binfmt.rst

@@ -75,7 +75,6 @@ pointer to a write-able instance of :c:struct:`binfmt_s`.
       int (*load)(FAR struct binary_s *bin); /* Verify and load binary into memory */
     };
 
-
   The ``load`` method is used to load the binary format into memory. It
   returns either ``OK`` (0) meaning that the binary object was loaded
   successfully, or a negated ``errno`` indicating why the object was not

Documentation/components/drivers/block/index.rst

@@ -38,4 +38,3 @@ Block device drivers have these properties:
 -  **Examples**. ``drivers/loop.c``,
    ``drivers/mmcsd/mmcsd_spi.c``, ``drivers/ramdisk.c``, etc.
 
-

Documentation/components/drivers/character/keypad.rst

@@ -140,4 +140,3 @@ application decoding interfaces.
 these interfaces. These stream interfaces are defined in
 ``include/nuttx/streams.h``.
 
-

Documentation/components/drivers/character/note.rst

@@ -165,7 +165,6 @@ Notectl Device (``/dev/notectl``)
   :return: If success, 0 (``OK``) is returned and the given IRQ filter mode is set as the current settings.
     If failed, a negated ``errno`` is returned.
 
-
 .. _noteram:
 
 Noteram Device (``/dev/note``)
@@ -174,7 +173,6 @@ Noteram Device (``/dev/note``)
   ``/dev/note`` is the device to get the trace (instrumentation) data.
   The device has read function to get the data and ioctl function to control the buffer mode.
 
-
 ``/dev/note`` Header Files
 --------------------------
 

Documentation/components/drivers/character/timer.rst

@@ -81,7 +81,6 @@ The first necessary thing to be done in order to use the timer driver in an appl
 
   #include <nuttx/timers/timer.h>
 
-
 At an application level, the timer functionalities may be accessed through ``ioctl`` systems calls. The available ``ioctl`` commands are:
 
  * :c:macro:`TCIOC_START`
@@ -140,8 +139,6 @@ These ``struct timer_ops_s`` keeps pointers to the implementation of each operat
                               FAR uint32_t *maxtimeout);
    };
 
-
-
 Since  ``ioctl`` system calls expect a file descriptor, before using these commands, it's necessary to open the timer device special file in order to get a file descriptor. The following snippet demonstrates how to do so:
 
 .. code-block:: c
@@ -296,7 +293,6 @@ This command may be used like so:
       return EXIT_FAILURE;
     }
 
-
 .. c:macro:: TCIOC_MAXTIMEOUT
 
 The ``TCIOC_MAXTIMEOUT`` command calls the ``maxtimeout`` operation, which is described below.
@@ -328,6 +324,5 @@ This command may be used like so:
 
   printf("Maximum supported timeout: %" PRIu32 "\n", max_timeout);
 
-
 Those snippets were taken from the Example which provides a great resource to demonstrate how to use those ``ioctl`` commands.
 

Documentation/components/drivers/character/watchdog.rst

@@ -82,7 +82,6 @@ The previously selected example will basically do the following:
 * Ping (feed the dog) during the ``pingtime`` with a delay of ``pingdelay`` and print out the wdt status in case debug was enabled.
 * Enter into an endless loop without pinging. It will cause the watchdog timer to reset the chip on timeout, i.e., after timer expiration.
 
-
 The `example code <https://github.com/apache/incubator-nuttx-apps/blob/master/examples/watchdog/watchdog_main.c>`_  may be explored, its path is at ``/examples/watchdog/watchdog_main.c`` in the apps' repository.
 
 In NuttX, the watchdog timer driver is a character driver and when a chip supports multiple watchdog timers, each one is accessible through its respective special file in ``/dev`` directory. Each watchdog timer is registered using a unique numeric identifier (i.e. ``/dev/watchdog0``, ``/dev/watchdog1``, ...).
@@ -108,7 +107,6 @@ The first necessary thing to be done in order to use the watchdog timer driver i
 
   #include <nuttx/timers/watchdog.h>
 
-
 At an application level, the watchdog timer functionalities may be accessed through ``ioctl`` systems calls. These ``ioctl`` commands internally call lower-half layer operations and the parameters are forwarded to these operations through the ``ioctl`` system call. The example provides a great resource to demonstrate how to use those ``ioctl`` commands. The available ``ioctl`` commands are:
 
 .. c:macro:: WDIOC_START

Documentation/components/drivers/special/syslog.rst

@@ -2,7 +2,6 @@
 SYSLOG
 ======
 
-
 SYSLOG Interfaces
 =================
 

Documentation/components/nxgraphics/appendix.rst

@@ -440,7 +440,6 @@ CONFIG_NXFONT_SANS23X27 for examaples:
       NULL
     };
 
-
 NX Test Coverage
 ================
 

Documentation/components/nxgraphics/nx.rst

@@ -716,4 +716,3 @@ Move a rectangular region within the window.
 
 .. _nx-tool-kit-nxtk-1:
 
-

Documentation/components/nxgraphics/nxcursor.rst

@@ -47,4 +47,3 @@ NX Cursor Support (``NXCURSOR``)
 
   :return: OK on success; ERROR on failure with errno set appropriately.
 
-

Documentation/components/nxgraphics/nxfonts.rst

@@ -33,7 +33,6 @@ NXFONTS types
       FAR const uint8_t *bitmap;     /* Pointer to the character bitmap */
     };
 
-
 .. c:struct:: nx_fontset_s
 
   This structure describes one contiguous grouping of glyphs that can be

Documentation/components/nxgraphics/nxgl.rst

@@ -117,7 +117,6 @@ NXGL Types
                     FAR const struct nxgl_point_s *v1, \
                     FAR const struct nxgl_point_s *v2);
 
-
  Add two 2x1 vectors and save the result to a third.
 
 .. c:function:: void nxgl_vectsubtract(FAR struct nxgl_point_s *dest, \
@@ -247,7 +246,6 @@ NXGL Types
 .. c:function:: void nxgl_circletraps(FAR const struct nxgl_point_s *center, nxgl_coord_t radius, \
                      FAR struct nxgl_trapezoid_s *circle);
 
-
   Given a description of a a circle, return 8 trapezoids
   that can be used to fill the circle by
   :c:func:`nx_fillcircle` and other interfaces.

Documentation/components/nxgraphics/nxtk.rst

@@ -436,7 +436,6 @@ these sub-windows to be managed more-or-less independently:
                      FAR const struct nx_callback_s *cb, \
                      FAR void *arg);
 
-
   Create a tool bar at the top of the specified framed
   window.
 
@@ -468,7 +467,6 @@ these sub-windows to be managed more-or-less independently:
 .. c:function:: int nxtk_filltoolbar(NXTKWINDOW hfwnd, FAR const struct nxgl_rect_s *rect, \
                      nxgl_mxpixel_t color[CONFIG_NX_NPLANES]);
 
-
   Fill the specified rectangle in the toolbar sub-window
   with the specified color.
 
@@ -487,7 +485,6 @@ these sub-windows to be managed more-or-less independently:
                     unsigned int plane, FAR uint8_t *dest, \
                     unsigned int deststride);
 
-
   Get the raw contents of graphic memory within a
   rectangular region. NOTE: Since raw graphic memory is returned, the
   returned memory content may be the memory of windows above this one and
@@ -530,7 +527,6 @@ these sub-windows to be managed more-or-less independently:
                          nxgl_coord_t width, nxgl_mxpixel_t color[CONFIG_NX_NPLANES], \
                          uint8_t caps);
 
-
   Fill the specified line in the toolbar sub-window with
   the specified color. This is simply a wrapper that uses
   ``nxgl_splitline()`` to break the line into trapezoids and then calls
@@ -558,7 +554,6 @@ these sub-windows to be managed more-or-less independently:
       #define NX_LINECAP_PT2   0x02  /* Line cap on pt2 on of the vector only */
       #define NX_LINECAP_BOTH  0x03  /* Line cap on both ends of the vector only */
 
-
   :return: ``OK`` on success; ``ERROR`` on failure with
     ``errno`` set appropriately
 
@@ -650,4 +645,3 @@ these sub-windows to be managed more-or-less independently:
 
 .. _nx-fonts-support-nxfonts-1:
 
-

Documentation/components/nxgraphics/sample.rst

@@ -27,4 +27,3 @@ Linux/Cygwin-based NuttX simulator. Instructions are provided for
 building that simulation are provided in `Appendix C <#testcoverage>`__
 of this document.
 
-

Documentation/components/power.rst

@@ -186,7 +186,6 @@ All PM interfaces are declared in the file ``include/nuttx/power/pm.h``.
 Callbacks
 =========
 
-
 .. c:struct:: pm_callback_s
 
   This struct includes the pointers to the driver

Documentation/contributing/coding_style.rst

@@ -920,7 +920,6 @@ conditional compilation does *not* cause any change to the indentation.
     ...
     #endif /* __INCLUDE_SOMEHEADER_H */
 
-
 Parentheses
 ===========
 
@@ -1146,7 +1145,6 @@ Parameters and Local Variables
       return ret;
     }
 
-
 **NOTE:** You will see the local variable named ``ret`` is frequently
 used in the code base for the name of a local variable whose value will
 be returned or to received the returned value from a called function.
@@ -2392,7 +2390,6 @@ Appendix
 C Source File Structure
 =======================
 
-
 .. code-block:: c
 
    /****************************************************************************
@@ -2430,7 +2427,6 @@ C Source File Structure
 
 *All C pre-processor macros are defined here.*
 
-
 .. code-block:: c
 
    /****************************************************************************

Documentation/contributing/making-changes.rst

@@ -28,15 +28,13 @@ Here's how to do it:
    If you don't have a `GitHub <https://www.github.com>`_ account, it's free to
    sign up.
 
-
 #. Fork the Projects
 
    Visit both these links and hit the Fork button in the upper right of the page:
 
    * `NuttX <https://github.com/apache/incubator-nuttx/>`_
    * `NuttX Apps <https://github.com/apache/incubator-nuttx-apps/>`_
 
-
 #. Clone the Repositories
 
    On the GitHub web page for your forked ``incubator-nuttx`` project, copy the clone url – get it by hitting the
@@ -66,7 +64,6 @@ Here's how to do it:
        $ git checkout -b test/my-new-branch
        $ git push
 
-
 Git Workflow With an Upstream Repository
 ----------------------------------------
 
@@ -162,7 +159,6 @@ maybe doing that several times. Then when everything works, I get my branch read
        $ git commit my-file.c
        $ git push
 
-
 Submitting Your Changes to NuttX
 --------------------------------
 

Documentation/guides/drivers.rst

@@ -143,7 +143,6 @@ modification.
         200aaa90: 0000 0000 0000 0000 0000 0000 0000 0000  ................
         200aaaa0: 0000 0000 0000 0000                      ........
 
-
 NuttX Drivers as a Reference
 ----------------------------
 

Documentation/guides/nfs.rst

@@ -190,7 +190,6 @@ called ``/export``.
 
   # sudo mkdir /export
 
-
 It is important that ``/export`` directory allow access to everyone (777
 permissions) as we will be accessing the NFS share from the client with
 no authentication.
@@ -280,5 +279,4 @@ And also we can verify if NFS is running in the system with:
        100021   3   tcp   1629  nlockmgr
        100021   4   tcp   1629  nlockmgr
 
-
 Now your NFS sever is sharing ``/export`` directory to be accessed.

Documentation/guides/tasktraceuser.rst

@@ -30,7 +30,6 @@ The following configurations must be enabled.
 - ``CONFIG_SYSTEM_TRACE`` : Enables "``trace``" command
 - ``CONFIG_SYSTEM_SYSTEM`` : Enables "``system``" command (required by :ref:`trace_cmd`)
 
-
 The following configurations are configurable parameters for trace.
 
 - ``CONFIG_SCHED_INSTRUMENTATION_FILTER_DEFAULT_MODE``
@@ -81,7 +80,6 @@ Getting the trace
 
 Trace is started by the following command.
 
-
 .. code-block::
 
   nsh> trace start
@@ -98,7 +96,6 @@ If you want to get the trace while executing some command, the following command
 
   nsh> trace cmd <command> [<args>...]
 
-
 Displaying the trace result
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
@@ -130,7 +127,6 @@ This will get the trace results like the following:
   <noname>-0   [0]   7.650000000: irq_handler_entry: irq=15
       :
 
-
 By using the logging function of your terminal software, the trace result can be saved into the host environment and it can be used as the input for `"Trace Compass" <https://www.eclipse.org/tracecompass/>`_.
 
 If the target has a storage, the trace result can be stored into the file by using the following command.
@@ -140,12 +136,10 @@ It also can be used as the input for "Trace Compass" by transferring the file in
 
   nsh> trace dump <file name>
 
-
 To display the trace result by `"Trace Compass" <https://www.eclipse.org/tracecompass/>`_, choose ``File`` -> ``Open Trace`` menu to specify the trace data file name.
 
 .. image:: image/trace-compass-screenshot.png
 
-
 Trace command description
 =========================
 
@@ -197,7 +191,6 @@ To use this command, ``CONFIG_SYSTEM_SYSTEM`` needs to be enabled.
 
   trace cmd [-c] <command> [<args>...]
 
-
 - ``-c`` : Continue the previous trace.
   The trace data is not cleared before starting new trace.
 
@@ -231,7 +224,6 @@ If the task trace is running, it is stopped before the output.
 - ``<filename>`` : Specify the filename to save the trace result.
   If not specified, the trace result is displayed to console.
 
-
 .. _trace_mode:
 
 trace mode

Documentation/guides/usbtrace.rst

@@ -188,8 +188,6 @@ Application Configuration -> NSH LIbrary     .
 .                                            with the usbmon_start and usbmon_stop commands from the NSH console.
 ===========================================  ===================================================
 
-
-
 ===============================================   ============================================
 Application Configuration -> System NSH Add-Ons   .
 ``CONFIG_USBMONITOR=y`` 	                        Enable the USB monitor daemon
@@ -210,7 +208,6 @@ Application Configuration -> System NSH Add-Ons   .
 ``CONFIG_USBMONITOR_TRACEINTERRUPTS=y``           .
 ===============================================   ============================================
 
-
 NOTE: If USB debug output is also enabled, both outputs will appear on
 the serial console. However, the debug output will be asynchronous with
 the trace output and, hence, difficult to interpret.