From: "Otavio Salvador" <otavio.salvador@ossystems.com.br>
To: c.sarmat@gmail.com
Cc: meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] #meta-freescale
Date: Fri, 16 Apr 2021 21:53:58 -0300 [thread overview]
Message-ID: <CAP9ODKrap1aO4k_cV3a3qxLFP+1ztRhDXR5HpOrFyiSQ7FT0Mg@mail.gmail.com> (raw)
In-Reply-To: <jcDG.1618582208052080433.8rLz@lists.yoctoproject.org>
Em sex., 16 de abr. de 2021 às 11:10, <c.sarmat@gmail.com> escreveu:
>
> After the commit d6cb0a63d1a77da21e7f9cb7ca6561371b3fc896 the functionality that inserts the configuration from the file deviceconfig.cfg to .conf was broken. I guess it is related to changing order of tasks.
Issue reported here: https://github.com/Freescale/meta-freescale/issues/733
Please provide any information there.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750
prev parent reply other threads:[~2021-04-17 0:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 14:10 #meta-freescale c.sarmat
2021-04-17 0:53 ` Otavio Salvador [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP9ODKrap1aO4k_cV3a3qxLFP+1ztRhDXR5HpOrFyiSQ7FT0Mg@mail.gmail.com \
--to=otavio.salvador@ossystems.com.br \
--cc=c.sarmat@gmail.com \
--cc=meta-freescale@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).