[riot-commits] [RIOT-OS/RIOT] 6e1c50: sys/auto_init: Fixed initialization of sht1x

José Alamos jialamos at uc.cl
Fri Nov 2 10:55:55 CET 2018


  Branch: refs/heads/master
  Home:   https://github.com/RIOT-OS/RIOT
  Commit: 6e1c50a1e3cf467eb2eefd33be51085320cde4da
      https://github.com/RIOT-OS/RIOT/commit/6e1c50a1e3cf467eb2eefd33be51085320cde4da
  Author: Marian Buschsieweke <marian.buschsieweke at ovgu.de>
  Date:   2018-10-26 (Fri, 26 Oct 2018)

  Changed paths:
    M sys/auto_init/auto_init.c

  Log Message:
  -----------
  sys/auto_init: Fixed initialization of sht1x

 - the driver for sht1x is initialized two times
 - the second initialization is done only when SAUL is used, but sht1x needs
   to be initialized in any case. (SAUL registration is also done there, but
   only when SAUL is actually being used.)

This commit fixes both.


  Commit: be6b705b38ccb451218e6d935f0fc72cf1c83db0
      https://github.com/RIOT-OS/RIOT/commit/be6b705b38ccb451218e6d935f0fc72cf1c83db0
  Author: Marian Buschsieweke <marian.buschsieweke at ovgu.de>
  Date:   2018-10-29 (Mon, 29 Oct 2018)

  Changed paths:
    M sys/auto_init/auto_init.c
    M sys/auto_init/saul/auto_init_sht1x.c

  Log Message:
  -----------
  sys/auto_init: Improved doc on sht1x auto init

The auto initialization of the sht1x module differs from the initialization of
other sensors, but previously no documentation pointed that out. This lack of
documentation led to a bug being introduced. This commit provides the previously
missing documentation.


  Commit: 6d8826e448047e63ae57d5faafaf728e1b3957ee
      https://github.com/RIOT-OS/RIOT/commit/6d8826e448047e63ae57d5faafaf728e1b3957ee
  Author: José Alamos <jialamos at uc.cl>
  Date:   2018-11-02 (Fri, 02 Nov 2018)

  Changed paths:
    M sys/auto_init/auto_init.c
    M sys/auto_init/saul/auto_init_sht1x.c

  Log Message:
  -----------
  Merge pull request #10267 from maribu/autoinit_fix

sys/auto_init: Fixed initialization of sht1x


Compare: https://github.com/RIOT-OS/RIOT/compare/cf24def63fdd...6d8826e44804
      **NOTE:** This service has been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/

      Functionality will be removed from GitHub.com on January 31st, 2019.


More information about the commits mailing list