Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix NXP unfiltered analog in compile error. #3

Merged
merged 1 commit into from
Apr 24, 2013

Conversation

oampo
Copy link
Contributor

@oampo oampo commented Apr 24, 2013

There is a typo which prevents the NXP analog in from compiling when median filtering is disabled. This is a quick one-liner to fix that.

emilmont added a commit that referenced this pull request Apr 24, 2013
Fix NXP unfiltered analog in compile error.
@emilmont emilmont merged commit 865ffcb into ARMmbed:master Apr 24, 2013
@oampo oampo deleted the bugfix-unfiltered-analog-in branch July 2, 2013 09:48
PrzemekWirkus added a commit that referenced this pull request Oct 20, 2014
PrzemekWirkus added a commit that referenced this pull request Feb 16, 2015
0xc0170 pushed a commit that referenced this pull request May 26, 2015
Pull in upstream changes
0xc0170 pushed a commit that referenced this pull request Jun 16, 2015
Update my fork with original
c1728p9 pushed a commit to c1728p9/mbed-os that referenced this pull request Jul 27, 2016
Refactored serial_api implementation.
@mmahadevan108 mmahadevan108 mentioned this pull request Oct 12, 2016
1 task
SeppoTakalo pushed a commit that referenced this pull request Nov 9, 2016
removed static-declarations from header
SeppoTakalo pushed a commit that referenced this pull request Nov 9, 2016
Add <stdint.h> include to header
geky pushed a commit to geky/mbed that referenced this pull request Jan 20, 2017
Filesystem: Added EEXIST reporting to mkdir through errno
sg- pushed a commit that referenced this pull request Feb 17, 2017
* Adding Cortex-A support for gnuarmeclipse
* Preventing '-mthumb' from being added to Cortex-A builds.
Previously, both '-mthumb' and '-marm' were being supplied to the
compiler (in that order). Because '-marm' came last, the compiler
respected this option. This change makes it so '-mthumb' is added for
all 'Cortex-M' targets only.
* Renaming to capital .S for Eclipse compatibility
@tung7970 tung7970 mentioned this pull request May 15, 2017
3 tasks
donatieng referenced this pull request in donatieng/mbed-os Mar 1, 2018
adbridge pushed a commit that referenced this pull request Mar 2, 2018
* Review fixes. Changed apn, username and password to be dynamically allocated.
cmonr pushed a commit that referenced this pull request Apr 4, 2018
@cmonr cmonr mentioned this pull request Aug 7, 2018
geky added a commit to geky/mbed that referenced this pull request Aug 25, 2018
Change driver initialization behavior:
@Crzyrndm Crzyrndm mentioned this pull request Feb 12, 2019
petroborys pushed a commit to petroborys/mbed-os that referenced this pull request Jun 4, 2019
hugueskamba referenced this pull request in hugueskamba/mbed-os Jul 2, 2019
* Move private stuff into internal dir

* Fix relative paths

* Add Doxygen

* Update copyright
artokin pushed a commit that referenced this pull request Jul 3, 2019
hugueskamba referenced this pull request in hugueskamba/mbed-os Jul 3, 2019
* Move private stuff into internal dir

* Fix relative paths

* Add Doxygen

* Update copyright
evedon pushed a commit to evedon/mbed-os that referenced this pull request Jul 5, 2019
The minimal-printf implementation supports a number of length modifiers
(j, z and t) that are not supported by the native mbed OS libc
implementation. The compliance test has tests for these modifiers, which
means that it isn't possible to check the output of mbed-printf against
a known good implementation (libc's printf) when running on mbed OS.
This, in turn, can give the impression that the tests for these
modifiers pass, when that might not be the case. To address this issue,
this PR removes the tests for these modifiers in mbed OS.

This PR was created because some of the tests for these modifiers
actually fail in Linux, for example:

```
>>> Running case ARMmbed#3: 'printf %u'...
hhu: 0
hhu: 0
hhu: 255
hhu: 255
hu: 0
hu: 0
hu: 65535
hu: 65535
u: 0
u: 0
u: 4294967295
u: 4294967295
lu: 0
lu: 0
lu: 4294967295
lu: 4294967295
llu: 0
llu: 0
llu: 18446744073709551615
llu: 18446744073709551615
ju: 0
ju: 0
ju: 4294967295
ju: 18446744073709551615
:188::FAIL: Expected 7 Was 16
>>> 'printf %u': 0 passed, 1 failed with reason 'Assertion Failed'
```
hugueskamba referenced this pull request in hugueskamba/mbed-os Jul 9, 2019
The minimal-printf implementation supports a number of length modifiers
(j, z and t) that are not supported by the native mbed OS libc
implementation. The compliance test has tests for these modifiers, which
means that it isn't possible to check the output of mbed-printf against
a known good implementation (libc's printf) when running on mbed OS.
This, in turn, can give the impression that the tests for these
modifiers pass, when that might not be the case. To address this issue,
this PR removes the tests for these modifiers in mbed OS.

This PR was created because some of the tests for these modifiers
actually fail in Linux, for example:

```
>>> Running case #3: 'printf %u'...
hhu: 0
hhu: 0
hhu: 255
hhu: 255
hu: 0
hu: 0
hu: 65535
hu: 65535
u: 0
u: 0
u: 4294967295
u: 4294967295
lu: 0
lu: 0
lu: 4294967295
lu: 4294967295
llu: 0
llu: 0
llu: 18446744073709551615
llu: 18446744073709551615
ju: 0
ju: 0
ju: 4294967295
ju: 18446744073709551615
:188::FAIL: Expected 7 Was 16
>>> 'printf %u': 0 passed, 1 failed with reason 'Assertion Failed'
```
evedon pushed a commit that referenced this pull request Jul 11, 2019
evedon pushed a commit to evedon/mbed-os that referenced this pull request Jul 15, 2019
The minimal-printf implementation supports a number of length modifiers
(j, z and t) that are not supported by the native mbed OS libc
implementation. The compliance test has tests for these modifiers, which
means that it isn't possible to check the output of mbed-printf against
a known good implementation (libc's printf) when running on mbed OS.
This, in turn, can give the impression that the tests for these
modifiers pass, when that might not be the case. To address this issue,
this PR removes the tests for these modifiers in mbed OS.

This PR was created because some of the tests for these modifiers
actually fail in Linux, for example:

```
>>> Running case ARMmbed#3: 'printf %u'...
hhu: 0
hhu: 0
hhu: 255
hhu: 255
hu: 0
hu: 0
hu: 65535
hu: 65535
u: 0
u: 0
u: 4294967295
u: 4294967295
lu: 0
lu: 0
lu: 4294967295
lu: 4294967295
llu: 0
llu: 0
llu: 18446744073709551615
llu: 18446744073709551615
ju: 0
ju: 0
ju: 4294967295
ju: 18446744073709551615
:188::FAIL: Expected 7 Was 16
>>> 'printf %u': 0 passed, 1 failed with reason 'Assertion Failed'
```
jh6186 added a commit to andrewc-arm/mbed-os that referenced this pull request Jan 6, 2020
Signed-off-by: PARKJIHOON <[email protected]>
andrewc-arm pushed a commit to andrewc-arm/mbed-os that referenced this pull request Jan 7, 2020
andrewc-arm pushed a commit to andrewc-arm/mbed-os that referenced this pull request Jan 8, 2020
LMESTM pushed a commit to LMESTM/mbed that referenced this pull request Jan 8, 2020
mbed-cloud-client-example R1.3.1-GA
andrewc-arm pushed a commit to andrewc-arm/mbed-os that referenced this pull request Jan 13, 2020
andrewc-arm pushed a commit to andrewc-arm/mbed-os that referenced this pull request Jan 14, 2020
andrewc-arm pushed a commit to andrewc-arm/mbed-os that referenced this pull request Jan 16, 2020
andrewc-arm pushed a commit to andrewc-arm/mbed-os that referenced this pull request Jan 21, 2020
andrewc-arm pushed a commit to andrewc-arm/mbed-os that referenced this pull request Jan 22, 2020
adbridge pushed a commit that referenced this pull request Feb 5, 2020
Signed-off-by: PARKJIHOON <[email protected]>
RyoheiHagimoto pushed a commit to RyoheiHagimoto/mbed-os that referenced this pull request Mar 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants