binfmt_execmodule() calls to sched_releasttcb() was not updated to use the second, thread type parameter

git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@5779 42af7a65-404d-4744-a932-0658087f49c3

configs/open1788/knsh/defconfig

@@ -191,8 +191,7 @@ CONFIG_LPC17_GPDMA=y
 #
 # SDIO Configuration
 #
-# CONFIG_SDIO_DMA=y
-CONFIG_SDIO_DMAPRIO=0x0
+# CONFIG_SDIO_DMA is not defined
 # CONFIG_SDIO_WIDTH_D1_ONLY is not set
 
 #

configs/open1788/nsh/defconfig

@@ -185,8 +185,7 @@ CONFIG_LPC17_GPDMA=y
 #
 # SDIO Configuration
 #
-# CONFIG_SDIO_DMA=y
-CONFIG_SDIO_DMAPRIO=0x0
+# CONFIG_SDIO_DMA is not defined
 # CONFIG_SDIO_WIDTH_D1_ONLY is not set
 
 #

configs/open1788/scripts/memory.ld

@@ -57,7 +57,8 @@
  *
  * For the same reasons, the maximum size of the SRAM mapping is limited to
  * 4KB.  Both of these alignment limitations could be reduced by using
- * multiple regions to map the FLASH/SDRAM range.
+ * multiple regions to map the FLASH/SDRAM range or perhaps with some
+ * clever use of subregions.
  *
  * A detailed memory map for the 64KB CPU SRAM region is as follows:
  *

configs/sam3u-ek/scripts/memory.ld

@@ -58,7 +58,8 @@
  *
  * For the same reasons, the maximum size of the SRAM mapping is limited to
  * 4KB.  Both of these alignment limitations could be reduced by using
- * multiple regions to map the FLASH/SDRAM range.
+ * multiple regions to map the FLASH/SDRAM range or perhaps with some
+ * clever use of subregions.
  *
  * A detailed memory map for the 16Kb SRAM region is as follows:
  *

configs/stm32f4discovery/scripts/memory.ld

@@ -65,7 +65,8 @@
  *
  * For the same reasons, the maximum size of the SRAM mapping is limited to
  * 4KB.  Both of these alignment limitations could be reduced by using
- * multiple regions to map the FLASH/SDRAM range.
+ * multiple regions to map the FLASH/SDRAM range or perhaps with some
+ * clever use of subregions.
  *
  * A detailed memory map for the 112KB SRAM region is as follows:
  *