release-notes: removed appending space characters

Author: haukepetersen

release-notes.txt

@@ -883,15 +883,15 @@ provided by RIOT.
 
 About this release:
 ===================
-This release was focused primarily on fixing bugs, but also adds two new 
+This release was focused primarily on fixing bugs, but also adds two new
 supported radio transceivers: CC2420 and CC2538.
-This new radio support allows to new interoperability tests with other OS, 
-allowing code size comparison and overall network performance for 
+This new radio support allows to new interoperability tests with other OS,
+allowing code size comparison and overall network performance for
 platforms based on these radios.
 
 About 198 pull requests with about 325 commits have been merged since the
-last release and about 65 issues have been solved. 46 people contributed with 
-code in 112 days. 632 files have been touched with 19863 insertions and 
+last release and about 65 issues have been solved. 46 people contributed with
+code in 112 days. 632 files have been touched with 19863 insertions and
 3682 deletions.
 
 
@@ -922,7 +922,7 @@ Packages
 ---
 + Added statistics for TLSF package (#5418)
 + Added U8g2 library for monochrome displays (#5549)
-* Added on-the-fly content creation for CCN-lite. 
+* Added on-the-fly content creation for CCN-lite.
 
 
 Platforms
@@ -931,23 +931,23 @@ Platforms
 + Added support for Libellium's waspmote-pro board.
 + Added support for the iotlab A8/M3 node (https://www.iot-lab.info/hardware/a8/)
 + Added initial and rudimentary port for TI cc2650stk "SensorTag" (#4675)
-+ Split Zolertia Remote support into Remote Prototype A (remote-pa) and 
++ Split Zolertia Remote support into Remote Prototype A (remote-pa) and
 Remote Revision A (remote-reva)
 
 Drivers
 ---
 + Texas Instruments CC2538 RF driver (PR #5291)
 + Texas Instruments CC2420 RF driver (PR #5591)
 + Bosch BM180 sensor.
-+ Added XBee optional AES encryption support 
++ Added XBee optional AES encryption support
 
 System libraries
 ---
 * Several xtimer bug fixes
 
 Build System
 ---
-+ Ubuntu 16.04 packaged gcc-arm-none-eabi toolchain can now be used to compile 
++ Ubuntu 16.04 packaged gcc-arm-none-eabi toolchain can now be used to compile
 RIOT for ARM boards
 
 Other
@@ -961,54 +961,54 @@ API changes
 Fixed Issues from the last release
 ==================================
 #3824: native: gnrc: hardcore pinging crashes.
-#4583: cpp11: clang doesn't allow mutex_t to be used with constexpr All 
+#4583: cpp11: clang doesn't allow mutex_t to be used with constexpr All
 cpp11-* tests fail with clang.
-#5388: gnrc_sixlowpan_iphc_nhc: receiving NHC compressed UDP 
+#5388: gnrc_sixlowpan_iphc_nhc: receiving NHC compressed UDP
 packets hits assert in IPv6 (Fixed by #5281).
 
 
 Known Issues
 ==========
 #3075: nhdp: unnecessary microsecond precision NHDP works with timer
- values of microsecond precision which is not required. Changing to lower 
+ values of microsecond precision which is not required. Changing to lower
  precision would save some memory.
 #3086: Max. packet length for AT86RF2XX
-#4048: potential racey memory leak According to the packet buffer stats, 
-flood-pinging a multicast destination may lead to a memory leak due to a 
-race condition. However, it seems to be a rare case and a completely filled 
+#4048: potential racey memory leak According to the packet buffer stats,
+flood-pinging a multicast destination may lead to a memory leak due to a
+race condition. However, it seems to be a rare case and a completely filled
 up packet buffer was not observed.
-#5005: ndp: router advertisement sent with global address Under some 
-circumstances a router might send RAs with GUAs. While they are ignored 
-on receive (as RFC 4861 specifies), RAs should have link-local addresses 
+#5005: ndp: router advertisement sent with global address Under some
+circumstances a router might send RAs with GUAs. While they are ignored
+on receive (as RFC 4861 specifies), RAs should have link-local addresses
  and not even be send out this way.
 #5007: gnrc icmpv6: Ping reply goes out the wrong interface
-#5055: cpuid: multiple radios will get same EUI-64 Nodes with multiple 
+#5055: cpuid: multiple radios will get same EUI-64 Nodes with multiple
 interfaces might get the same EUI-64 for them since they are generated from
  the same CPU ID.
- #5230: gnrc ipv6: multicast packets are not dispatched to the upper layers. 
+ #5230: gnrc ipv6: multicast packets are not dispatched to the upper layers.
 (Fix exists, but was postponed)
-#5390: pkg: OpenWSN does not compile This package still uses deprecated 
+#5390: pkg: OpenWSN does not compile This package still uses deprecated
 modules and was not tested for a long time.
 
 native related issues
 ---------------------
-#495: native not float safe When the FPU is used when an asynchronous 
-context switch occurs, either the stack gets corrupted or a floating point 
+#495: native not float safe When the FPU is used when an asynchronous
+context switch occurs, either the stack gets corrupted or a floating point
 exception occurs.
-#534: native debugging on osx fails Using valgrind or gdb with a nativenet 
-target in OSX leads to "the network" being stuck (gdb) or the whole process 
+#534: native debugging on osx fails Using valgrind or gdb with a nativenet
+target in OSX leads to "the network" being stuck (gdb) or the whole process
 being stuck (valgrind).
-#334: nativenet crashes when hammered Flood-pinging a native instance 
-from more than one host (either multiple threads on the host system or multiple 
+#334: nativenet crashes when hammered Flood-pinging a native instance
+from more than one host (either multiple threads on the host system or multiple
 other native instances), leads to a SEGFAULT.
 #2071; WIP: native: overdue fixes
 #4590: pkg: building relic with clang fails.
 #5432: native: valgrind fails
 
 other platform related issues
 -----------------------------
-#4560: make: clang is more pedantic than gcc oonf_api is not building with 
-clang. 
+#4560: make: clang is more pedantic than gcc oonf_api is not building with
+clang.
 (Partly solved by #4593)
 #4866: not all GPIO driver implementations are thread safe Due to non-atomic
  operations in the drivers some pin configurations might get lost.
@@ -1017,26 +1017,26 @@ clang.
 other issues
 ------------
 #1263: TLSF implementation contains (a) read-before-write error(s).
-#2761: core: define default flags If a thread is created without the 
-corresponding flag (CREATE_STACKTEST), the ps command will yield wrong 
+#2761: core: define default flags If a thread is created without the
+corresponding flag (CREATE_STACKTEST), the ps command will yield wrong
 numbers for the stack usage.
-#2927: core: Automatically select the lowest possible LPM mode Not all 
-available low power modes (LPMs) are implemented for each platform and the 
+#2927: core: Automatically select the lowest possible LPM mode Not all
+available low power modes (LPMs) are implemented for each platform and the
 concept of how the LPM is chosen needs some reconsideration.
-#2967: Makefile.features: location is not relevant for all features Provided 
+#2967: Makefile.features: location is not relevant for all features Provided
 features for the build system should be split up into a board and cpu specific part
-#4488: Making the newlib thread-safe When calling puts/printf after 
+#4488: Making the newlib thread-safe When calling puts/printf after
 thread_create(), the CPU hangs for DMA enabled uart drivers.
 #4841: xtimer: timer already in the list Under some conditions an xtimer can end
  up twice in the internal list of the xtimer module.
 #5338: xtimer: xtimer_now() not ISR safe For non-32-bit platforms.
 
 Special Thanks
 ===============
-We like to give our special thanks to all the companies that provided us with their 
-hardware for porting and testing, namely the people from (in alphabeticalorder): 
+We like to give our special thanks to all the companies that provided us with their
+hardware for porting and testing, namely the people from (in alphabeticalorder):
 Atmel, Freescale, Limifrog, Nordic, OpenMote, Phytec, SiLabs, UDOO,and Zolertia;
- and also companies that directly sponsored development time:Cisco Systems, 
+ and also companies that directly sponsored development time:Cisco Systems,
 Eistec, Ell-i, Enigeering Spirit, Nordic, FreshTemp LLC, and Phytec.
 
 More information
@@ -1045,15 +1045,15 @@ http://www.riot-os.org
 
 Mailing lists
 -------------
-* RIOT OS kernel developers list 
+* RIOT OS kernel developers list
  * devel@riot-os.org (http://lists.riot-os.org/mailman/listinfo/devel)
-* RIOT OS users list 
+* RIOT OS users list
  * users@riot-os.org (http://lists.riot-os.org/mailman/listinfo/users)
  * RIOT commits
   * commits@riot-os.org (http://lists.riot-os.org/mailman/listinfo/commits)
 * Github notifications
  * notifications@riot-os.org  (http://lists.riot-os.org/mailman/listinfo/notifications)
- 
+
 IRC
 ---
 * Join the RIOT IRC channel at: irc.freenode.net, #riot-os