From: Sven Ebenfeld <sven.ebenfeld@gmail.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
Daiane Angolini <daiane.list@gmail.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm][PATCH] linux-mfgtool: Prevent overwriting linux-imx deployments
Date: Tue, 16 Dec 2014 20:51:25 +0100 [thread overview]
Message-ID: <54908D3D.3050307@gmail.com> (raw)
In-Reply-To: <CAP9ODKqggM9yH0_OKf+mmXQrxzPM+CjKZSKHtGjGtpLg8RgeoA@mail.gmail.com>
Am 12.12.2014 um 13:50 schrieb Otavio Salvador:
> On Fri, Nov 21, 2014 at 9:11 AM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
>> On Fri, Nov 21, 2014 at 8:48 AM, Daiane Angolini <daiane.list@gmail.com> wrote:
>>> On Fri, Nov 21, 2014 at 4:06 AM, Sven Ebenfeld <sven.ebenfeld@gmail.com> wrote:
>>>
>>>>
>>>> Do you think it's possible to get it merged with a better commit log or
>>>> do you have a proposal where I should look for a better fix?
>>>
>>> I don´t have a better patch either, but _to merge or not to merge_ is
>>> up to Otavio.
>>>
>>> I can help with testing next week, if applicable.
>>
>> I want to debug this and see if I can come up with something...
>
> I really failed to reproduce the warnings; I built it using master for
> SabreSD and I built both the initramfs and runtime images and kernels
> without a issue.
>
> Is it possible, Sven, for you to try to come up with a way for me to
> reproduce the issue?
At the moment, I am unable to reproduce this problem as well.
This must have been a problem in my configuration. At least that is what
I think at the moment.
next prev parent reply other threads:[~2014-12-16 19:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 9:56 [meta-fsl-arm][PATCH] linux-mfgtool: Prevent overwriting linux-imx deployments Sven Ebenfeld
2014-11-19 15:07 ` Daiane Angolini
2014-11-21 6:06 ` Sven Ebenfeld
2014-11-21 10:48 ` Daiane Angolini
2014-11-21 11:11 ` Otavio Salvador
2014-12-12 12:50 ` Otavio Salvador
2014-12-16 19:51 ` Sven Ebenfeld [this message]
2014-12-16 19:52 ` Otavio Salvador
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=54908D3D.3050307@gmail.com \
--to=sven.ebenfeld@gmail.com \
--cc=daiane.list@gmail.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.