diff options
| author | Gregory Nutt <gnutt@nuttx.org> | 2014-01-15 11:05:15 -0600 |
|---|---|---|
| committer | Gregory Nutt <gnutt@nuttx.org> | 2014-01-15 11:05:15 -0600 |
| commit | 7367295fa7f5346b76a344002280609448e32807 (patch) | |
| tree | 64d55c909f802d328216c1bc8ddb5327ac56b23a /nuttx/ChangeLog | |
| parent | 5a76ae0ab3dcc7c120288fd4e48bf3d0b7cdad70 (diff) | |
| download | px4-nuttx-7367295fa7f5346b76a344002280609448e32807.tar.gz px4-nuttx-7367295fa7f5346b76a344002280609448e32807.tar.bz2 px4-nuttx-7367295fa7f5346b76a344002280609448e32807.zip | |
Misc changes from Richard Cochran
Diffstat (limited to 'nuttx/ChangeLog')
| -rw-r--r-- | nuttx/ChangeLog | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/nuttx/ChangeLog b/nuttx/ChangeLog index 3780ba61f..976164356 100644 --- a/nuttx/ChangeLog +++ b/nuttx/ChangeLog @@ -6463,5 +6463,6 @@ is not really important because up_disable_irq() is not really used for that purpose. But some spurions STM32 ADC interrupts have been reported to me and this turned out to be the cause in that case. My - concern not that up_disable_irq() works is that there may now be - unmasked bugs that leave devices in the disabled state? (2014-1-15). + concern now that up_disable_irq() works is that there may now be + unmasked bugs that leave devices in the disabled state? Thanks to + Manuel Stühn for the tip(2014-1-15). |