All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daiane Angolini <daiane.angolini@freescale.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
	Eric Nelson <eric.nelson@boundarydevices.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [RFC] default u-boot
Date: Thu, 10 Oct 2013 16:18:43 -0300	[thread overview]
Message-ID: <5256FD93.1000200@freescale.com> (raw)
In-Reply-To: <CAP9ODKpQ9ipEG8BUpK+yNjBVaDyZTRQrjywr6RJB6VuGm-vEaw@mail.gmail.com>

On 10/10/2013 04:16 PM, Otavio Salvador wrote:
> On Thu, Oct 10, 2013 at 4:10 PM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>> On 10/10/2013 10:44 AM, Otavio Salvador wrote:
>>> On Thu, Oct 10, 2013 at 1:31 PM, Eric Nelson
>>> <eric.nelson@boundarydevices.com> wrote:
>>>>
>>>> On 10/10/2013 09:28 AM, Otavio Salvador wrote:
>>>>>
>>>>> It seems the best would be if, instead of pushing to our u-boot GIT,
>>>>> it had regular updates in the u-boot-boundary recipes and point to
>>>>> newer revisions.
>>>>>
>>>>
>>>> We'll make sure to update with each switch in our production branch.
>>>
>>>
>>> Great; this is the way to go.
>>>
>>> Could you please update the current SRCREV and PV values to match the
>>> current state?
>>>
>>
>> This is essentially done... meta-fsl-arm-extra is only one patch behind
>> (a custom board).
>>
>> We're expecting to issue our next release after 2013.10 is finalized.
>
> Great; so PV might be updated? for 2013.07 I think.
>
> I think this was the root cause of Daiane's confusion as it points 2013.01.

Oh, good point.

It made me remember I was wondering yesterday night if we want to have a 
pattern/standard for the string added after kernel version for all 
providers!
(and how to descriver both u-boot and linux providers)

Because it's a mess today.



-- 
Daiane



  reply	other threads:[~2013-10-10 19:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-10  0:28 [RFC] default u-boot Daiane Angolini
2013-10-10  1:59 ` Eric Nelson
2013-10-10 12:47   ` Daiane Angolini
2013-10-10 14:26     ` Eric Nelson
2013-10-10 16:12       ` Daiane Angolini
2013-10-10 16:28         ` Otavio Salvador
2013-10-10 16:31           ` Eric Nelson
2013-10-10 17:44             ` Otavio Salvador
2013-10-10 19:10               ` Eric Nelson
2013-10-10 19:10                 ` Daiane Angolini
2013-10-10 19:35                   ` Eric Nelson
2013-10-11 11:27                     ` Daiane Angolini
2013-10-10 19:16                 ` Otavio Salvador
2013-10-10 19:18                   ` Daiane Angolini [this message]
2013-10-10 19:38                   ` Eric Nelson
2013-10-10 16:32 ` Dmitriy B.
2013-10-10 17:56   ` Daiane Angolini
2013-10-10 19:02     ` Haakon Stende
2013-10-10 19:08       ` 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=5256FD93.1000200@freescale.com \
    --to=daiane.angolini@freescale.com \
    --cc=eric.nelson@boundarydevices.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.