IMXRT1050 USDHC

Hello, I found a typo mistake in the USDHC driver related to the card detect pin. It is a pretty simple one. Can someone tell me how toapplay a patch for it. Or someone who know how to do it do the following changes and apply them. Thank you in advance! in file /arch/arm/src/imxrt/imxrt_usdhc.c

Incubator site link broken

Hi, The link to NuttX at https://incubator.apache.org/projects/ seems to be broken, I just get a 404 error. Has it been moved? //Pelle

Re: [DISCUSS] Wrapping up the Workflow document

The reason the workflow document has too much information is because it contains more than just the procedure to submit a PR/patch. It is intended for both committers and contributors. The "Workflow" section contains the necessary instructions to follow. > Here is my `gitlast` command (it helps m

RE: [DISCUSS] Wrapping up the Workflow document

Funny! I meant real streamlined work instruction. nothing ambiguous and nothing is not needed. Something along the lines of https://dev.px4.io/master/en/contribute/git_examples.html David -Original Message- From: Nathan Hartman [mailto:hartman.nat...@gmail.com] Sent: Wednesday, January

Re: [DISCUSS] Wrapping up the Workflow document

On Wed, Jan 29, 2020 at 10:14 AM David Sidrane wrote: > My general comment on the Workflow document is it is too much information > and comments. > > Perhaps it can be broken into patch Workflow, git Workflow and githup > Workflow and then just list the steps. > (Think in terms of a quckstart guid

[GitHub] [incubator-nuttx-testing] xiaoxiang781216 commented on issue #2: Multibranch pipeline job example

xiaoxiang781216 commented on issue #2: Multibranch pipeline job example URL: https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-579887092 @@liuguo09 please take a look. This is an automated message from the

RE: [DISCUSS] Wrapping up the Workflow document

My general comment on the Workflow document is it is too much information and comments. Perhaps it can be broken into patch Workflow, git Workflow and githup Workflow and then just list the steps. (Think in terms of a quckstart guide for nuttx workflow) In reading it I am still not clear on the w

Re: [DISCUSS] Wrapping up the Workflow document

On Wed, Jan 29, 2020 at 8:10 AM David Sidrane wrote: > Good tips! git is s powerful it is nice to lean other's tricks. > > Here is my `gitlast` command (it helps me answer the question: What was I > doing?) > > git for-each-ref --count=30 --sort=-committerdate > refs/heads/ --format='%(refnam

Re: NuttX at FOSDEM 2020

Thanks for the offer. If there is enough time for me to finish it I would gladly use the opportunity Regards Alin On Wed, Jan 29, 2020 at 2:59 PM Philippe Coval wrote: > On Wed, Jan 29, 2020 at 2:33 PM Alin Jerpelea wrote: > > > Hi, > > > > I tried to get a developer room and a talk for NuttX

Re: NuttX at FOSDEM 2020

On Wed, Jan 29, 2020 at 2:33 PM Alin Jerpelea wrote: > Hi, > > I tried to get a developer room and a talk for NuttX but I was rejected > Sorry to hear that, was it also in IoT room ? Anyway If you want to co-present NuttX in my session, It's doable, because I am not planning to give too much de

Re: NuttX at FOSDEM 2020

Hi, I tried to get a developer room and a talk for NuttX but I was rejected See you at FOSDEM Regards Alin On Tue, Jan 28, 2020 at 11:43 PM Philippe Coval < philippe.coval@gmail.com> wrote: > On Tue, Jan 28, 2020 at 9:02 PM Alan Carvalho de Assis > wrote: > > > Hi Brenan, > > > > Did you

RE: [DISCUSS] Wrapping up the Workflow document

Hi Abdelatif, Good tips! git is s powerful it is nice to lean other's tricks. Here is my `gitlast` command (it helps me answer the question: What was I doing?) git for-each-ref --count=30 --sort=-committerdate refs/heads/ --format='%(refname:short)' How's about we add a section to the docum