Build failed in Jenkins: NuttX-Nightly-Build #169

See Changes: -- [...truncated 481.30 KB...] open-amp.zip[<=> ] 0 --.-KB/s open-amp.zip[ <=>] 716.85K --.

Re: mbedtls

Hi, I’m concerned that you are discussion doing work outside of the Apache repositories. Why is the main issue here? Greg mentions that the apache report are not properly controlled and verified but I’m not 100% sure what he means by that. The PMC has control of them and only verified committe

Re: Release Notes for the NEXT version of NuttX

On Sat, May 23, 2020, 8:26 AM Xiang Xiao wrote: > > > > -Original Message- > > From: Abdelatif Guettouche > > Sent: Saturday, May 23, 2020 9:18 PM > > To: dev@nuttx.apache.org > > Subject: Re: Release Notes for the NEXT version of NuttX > > > > > Yes, it's better to accumulative all patc

RE: Release Notes for the NEXT version of NuttX

> -Original Message- > From: Abdelatif Guettouche > Sent: Saturday, May 23, 2020 9:18 PM > To: dev@nuttx.apache.org > Subject: Re: Release Notes for the NEXT version of NuttX > > > Yes, it's better to accumulative all patch for a specific release candidate > > in an issue/request in t

Re: Arm Kinetis: set_errno in nx_start with CONFIG_TLS_ALIGNED not set

PR #1105 should eliminate the primary cause of the error: fs_fdopen() will not longer set the errno  variable.  The secondary error, the uninitialized stack description, is still a problem. Since the errno value was only set before fs_fdopen() failed, this means that you system will still no

Re: Arm Kinetis: set_errno in nx_start with CONFIG_TLS_ALIGNED not set

PR #1105 should eliminate the primary cause of the error: fs_fdopen() will not longer set the errno  variable.  The secondary error, the uninitialized stack description, is still a problem. On 5/22/2020 10:19 PM, Gregory Nutt wrote: The new implementation of set_errno require all thread(incl

Re: Release Notes for the NEXT version of NuttX

> Yes, it's better to accumulative all patch for a specific release candidate > in an issue/request in the future release, then we can track each release > more easier. Commit wise, we would have the same history, or are you suggesting to squash all the backported commits? On Sat, May 23, 2020