Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

[Burton, Ross]

On 30 March 2017 at 19:06, Denys Dmytriyenko  wrote:

> "Known devil is better than unknown angel"? :)
>

Agreed, fwiw.  It's late and u-boot is quite important: cherry-pick the
patch for Pyro and master can upgrade once it has branched.

Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

[Otavio Salvador]

On Thu, Mar 30, 2017 at 4:12 PM, Philip Balister  wrote:
> I've got a machine under development that boots from the 2013.01 recipe
> and a bbappend. I don't think it is a problem moving to .03, but I don't
> know. I'm not sure how many other BSP's have done the same.

If it is a full mainline machine it should be smooth; otherwise
sending the patch to enable it in mainline is the best long term
solution. Keeping a patch on top a recipe is a decision which ends
with the maintenance burden at the developer adding the patch.

External layers should not delay the additions or upgrades of recipes
of OE-Core. If maintenance is a concern, upstreaming is the best
choice or fork the U-Boot and keep the fork with an independent cycle.

> Meanwhile, I understand the desire of others who have work upstreamed in
> u-boot they like to use with the next release.

And it has been a way to endorse the upstreaming effort to reduce the
maintenance work.

> How many u-boot releases are there a year? How do they line up with YP
> releases? Should we carry two u-boot versions, similar to what happens
> with the kernel?

Every two months now. I see no reason to carry two versions. OE-Core
provides the basis and every BSP layers can maintain their own
versions.

-- 
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

[Philip Balister]

On 03/30/2017 02:06 PM, Denys Dmytriyenko wrote:
> On Thu, Mar 30, 2017 at 04:12:08PM +0200, Marek Vasut wrote:
>> On 03/30/2017 03:24 PM, Denys Dmytriyenko wrote:
>>> On Thu, Mar 30, 2017 at 10:21:31AM +0200, Marek Vasut wrote:
 On 03/29/2017 11:56 PM, Denys Dmytriyenko wrote:
> On Mon, Mar 27, 2017 at 04:31:16PM +0200, Marek Vasut wrote:
>> On 03/27/2017 04:25 PM, Richard Purdie wrote:
>>> On Mon, 2017-03-27 at 16:22 +0200, Marek Vasut wrote:
 Upgrade U-Boot to the latest version.
>>>
>>> Wrong list and how does this compare to Ovatio's patch?
>>
>> I was not CCed on Otavio's patch :(
>
> Yeah, me neither, unfortunately - people just ignore maintainers file now.
>
> Good thing Ross copied me on the other discussion!
>
 Which other discussion ? :-(
>>>
>>> http://lists.openembedded.org/pipermail/openembedded-core/2017-March/134682.html
>>>
>> I see. I'm all for updating to 2017.03 , since it fixes the OMAP serial
>> bug too :)
> 
> "Known devil is better than unknown angel"? :)
> 

I've got a machine under development that boots from the 2013.01 recipe
and a bbappend. I don't think it is a problem moving to .03, but I don't
know. I'm not sure how many other BSP's have done the same.

Meanwhile, I understand the desire of others who have work upstreamed in
u-boot they like to use with the next release.

How many u-boot releases are there a year? How do they line up with YP
releases? Should we carry two u-boot versions, similar to what happens
with the kernel?

Philip
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

[Denys Dmytriyenko]

On Thu, Mar 30, 2017 at 04:12:08PM +0200, Marek Vasut wrote:
> On 03/30/2017 03:24 PM, Denys Dmytriyenko wrote:
> > On Thu, Mar 30, 2017 at 10:21:31AM +0200, Marek Vasut wrote:
> >> On 03/29/2017 11:56 PM, Denys Dmytriyenko wrote:
> >>> On Mon, Mar 27, 2017 at 04:31:16PM +0200, Marek Vasut wrote:
>  On 03/27/2017 04:25 PM, Richard Purdie wrote:
> > On Mon, 2017-03-27 at 16:22 +0200, Marek Vasut wrote:
> >> Upgrade U-Boot to the latest version.
> >
> > Wrong list and how does this compare to Ovatio's patch?
> 
>  I was not CCed on Otavio's patch :(
> >>>
> >>> Yeah, me neither, unfortunately - people just ignore maintainers file now.
> >>>
> >>> Good thing Ross copied me on the other discussion!
> >>>
> >> Which other discussion ? :-(
> > 
> > http://lists.openembedded.org/pipermail/openembedded-core/2017-March/134682.html
> > 
> I see. I'm all for updating to 2017.03 , since it fixes the OMAP serial
> bug too :)

"Known devil is better than unknown angel"? :)

-- 
Denys
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

[Marek Vasut]

On 03/30/2017 03:24 PM, Denys Dmytriyenko wrote:
> On Thu, Mar 30, 2017 at 10:21:31AM +0200, Marek Vasut wrote:
>> On 03/29/2017 11:56 PM, Denys Dmytriyenko wrote:
>>> On Mon, Mar 27, 2017 at 04:31:16PM +0200, Marek Vasut wrote:
 On 03/27/2017 04:25 PM, Richard Purdie wrote:
> On Mon, 2017-03-27 at 16:22 +0200, Marek Vasut wrote:
>> Upgrade U-Boot to the latest version.
>
> Wrong list and how does this compare to Ovatio's patch?

 I was not CCed on Otavio's patch :(
>>>
>>> Yeah, me neither, unfortunately - people just ignore maintainers file now.
>>>
>>> Good thing Ross copied me on the other discussion!
>>>
>> Which other discussion ? :-(
> 
> http://lists.openembedded.org/pipermail/openembedded-core/2017-March/134682.html
> 
I see. I'm all for updating to 2017.03 , since it fixes the OMAP serial
bug too :)

-- 
Best regards,
Marek Vasut
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

[Denys Dmytriyenko]

On Thu, Mar 30, 2017 at 10:21:31AM +0200, Marek Vasut wrote:
> On 03/29/2017 11:56 PM, Denys Dmytriyenko wrote:
> > On Mon, Mar 27, 2017 at 04:31:16PM +0200, Marek Vasut wrote:
> >> On 03/27/2017 04:25 PM, Richard Purdie wrote:
> >>> On Mon, 2017-03-27 at 16:22 +0200, Marek Vasut wrote:
>  Upgrade U-Boot to the latest version.
> >>>
> >>> Wrong list and how does this compare to Ovatio's patch?
> >>
> >> I was not CCed on Otavio's patch :(
> > 
> > Yeah, me neither, unfortunately - people just ignore maintainers file now.
> > 
> > Good thing Ross copied me on the other discussion!
> > 
> Which other discussion ? :-(

http://lists.openembedded.org/pipermail/openembedded-core/2017-March/134682.html

-- 
Denys
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

[Marek Vasut]

On 03/29/2017 11:56 PM, Denys Dmytriyenko wrote:
> On Mon, Mar 27, 2017 at 04:31:16PM +0200, Marek Vasut wrote:
>> On 03/27/2017 04:25 PM, Richard Purdie wrote:
>>> On Mon, 2017-03-27 at 16:22 +0200, Marek Vasut wrote:
 Upgrade U-Boot to the latest version.
>>>
>>> Wrong list and how does this compare to Ovatio's patch?
>>
>> I was not CCed on Otavio's patch :(
> 
> Yeah, me neither, unfortunately - people just ignore maintainers file now.
> 
> Good thing Ross copied me on the other discussion!
> 
Which other discussion ? :-(

-- 
Best regards,
Marek Vasut
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

[Denys Dmytriyenko]

On Wed, Mar 29, 2017 at 11:16:07PM +0100, Richard Purdie wrote:
> On Wed, 2017-03-29 at 17:56 -0400, Denys Dmytriyenko wrote:
> > On Mon, Mar 27, 2017 at 04:31:16PM +0200, Marek Vasut wrote:
> > > 
> > > On 03/27/2017 04:25 PM, Richard Purdie wrote:
> > > > 
> > > > On Mon, 2017-03-27 at 16:22 +0200, Marek Vasut wrote:
> > > > > 
> > > > > Upgrade U-Boot to the latest version.
> > > > Wrong list and how does this compare to Ovatio's patch?
> > > I was not CCed on Otavio's patch :(
> > Yeah, me neither, unfortunately - people just ignore maintainers file
> > now.
> > 
> > Good thing Ross copied me on the other discussion!
> 
> This raises a very valid point which is what any maintainers file is
> and what it is not.
> 
> The one that exists in meta-yocto today has a very specific meaning. I
> know there is discussion about moving it to OE-Core however if we do so
> I want to by *really* *really* clear about what being listed there
> means and does not mean.
> 
> As things stand right now, there is no requirement or advice in any of
> our guides to cc "maintainers". People struggle to send patches as it
> is and giving them more hoops to jump through doesn't seem like a
> brilliant idea to me. I know we can create a file with all kinds of
> path matching for files people care/don't care about but I worry this
> will descend into complicated scripts and people still getting upset
> when they were cc'd needlessly or weren't cc'd etc.
> 
> I also quite strongly dislike the "I own X, so only I can change it"
> type view, to be the maintainers are people who help look after
> specific areas in the absence of anyone else and help review patches
> that come in. They certainly get significant influence on things but
> the price for that is they also have to help fix issues and figure out
> ways of helping others with issues in that area.
> 
> So please think very carefully about what you want this "maintainers"
> file to be/not be as I worry its a huge can of worms we once tried in
> OE before...

Well, this reminds me of numerous discussions we've had in the past at several 
OEDEMs and OEDAMs about maintainers file and requirements/responsibilities it 
carries - unfortunately we never been able to resolve it one way or another. I 
guess we'll try finalizing it again with the renewed effort now...


As of u-boot - wasn't trying to claim ownership at all. In the past we've had 
a number of updates from TI, as it's a bootloader of choice for our platforms. 
Somehow I got assigned as a maintainer for the corresponding recipes. I know 
Otavio is also responsible for some changes there, from his involvement with 
Freescale. And at OEDEM last fall, I had a good conversation with Marek about 
u-boot recipes, we've discussed restructuring and re-versioning plans and 
since then he's copying me on his updates - I'm trying to review and/or test 
his changes as much as I can. That's all to it.

-- 
Denys
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

[Richard Purdie]

On Wed, 2017-03-29 at 17:56 -0400, Denys Dmytriyenko wrote:
> On Mon, Mar 27, 2017 at 04:31:16PM +0200, Marek Vasut wrote:
> > 
> > On 03/27/2017 04:25 PM, Richard Purdie wrote:
> > > 
> > > On Mon, 2017-03-27 at 16:22 +0200, Marek Vasut wrote:
> > > > 
> > > > Upgrade U-Boot to the latest version.
> > > Wrong list and how does this compare to Ovatio's patch?
> > I was not CCed on Otavio's patch :(
> Yeah, me neither, unfortunately - people just ignore maintainers file
> now.
> 
> Good thing Ross copied me on the other discussion!

This raises a very valid point which is what any maintainers file is
and what it is not.

The one that exists in meta-yocto today has a very specific meaning. I
know there is discussion about moving it to OE-Core however if we do so
I want to by *really* *really* clear about what being listed there
means and does not mean.

As things stand right now, there is no requirement or advice in any of
our guides to cc "maintainers". People struggle to send patches as it
is and giving them more hoops to jump through doesn't seem like a
brilliant idea to me. I know we can create a file with all kinds of
path matching for files people care/don't care about but I worry this
will descend into complicated scripts and people still getting upset
when they were cc'd needlessly or weren't cc'd etc.

I also quite strongly dislike the "I own X, so only I can change it"
type view, to be the maintainers are people who help look after
specific areas in the absence of anyone else and help review patches
that come in. They certainly get significant influence on things but
the price for that is they also have to help fix issues and figure out
ways of helping others with issues in that area.

So please think very carefully about what you want this "maintainers"
file to be/not be as I worry its a huge can of worms we once tried in
OE before...

Cheers,

Richard

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

[Denys Dmytriyenko]

On Mon, Mar 27, 2017 at 04:31:16PM +0200, Marek Vasut wrote:
> On 03/27/2017 04:25 PM, Richard Purdie wrote:
> > On Mon, 2017-03-27 at 16:22 +0200, Marek Vasut wrote:
> >> Upgrade U-Boot to the latest version.
> > 
> > Wrong list and how does this compare to Ovatio's patch?
> 
> I was not CCed on Otavio's patch :(

Yeah, me neither, unfortunately - people just ignore maintainers file now.

Good thing Ross copied me on the other discussion!

-- 
Denys
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

[Philip Balister]

Some background is needed 

Marex sent in the 2017.01 update after discussions in irc about timing
of u-boot releases and the YP release schedule. The 2017.03 release
would happen after oe-core passed the feature freeze. So, at the time
people felt the release should have 2017.01.

People consuming the u-boot recipe via a bbappends have been using
2017.01 for their bsp's. Changing at this time is potentially a pain
point, and has some technical risk on the release schedule.

On the other hand, people working to get their code upstream, might be
frustrated having to wait until fall to use a current u-boot release.

Should we go ahead and add the 2017.03 recipe and use DEFAULT_PREFERENCE
to turn it off?

Also, this would be a good time to determine who the maintainers of the
recipes are.

Philip


On 03/27/2017 10:32 AM, Marek Vasut wrote:
> Upgrade U-Boot to the latest version.
> 
> Signed-off-by: Marek Vasut 
> Cc: Denys Dmytriyenko 
> Cc: Richard Purdie 
> Cc: Ross Burton 
> ---
>  .../u-boot/{u-boot-common_2017.01.inc => u-boot-common_2017.03.inc} | 2 
> +-
>  .../u-boot/{u-boot-fw-utils_2017.01.bb => u-boot-fw-utils_2017.03.bb}   | 0
>  .../u-boot/{u-boot-mkimage_2017.01.bb => u-boot-mkimage_2017.03.bb} | 0
>  meta/recipes-bsp/u-boot/{u-boot_2017.01.bb => u-boot_2017.03.bb}| 0
>  4 files changed, 1 insertion(+), 1 deletion(-)
>  rename meta/recipes-bsp/u-boot/{u-boot-common_2017.01.inc => 
> u-boot-common_2017.03.inc} (86%)
>  rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.01.bb => 
> u-boot-fw-utils_2017.03.bb} (100%)
>  rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.01.bb => 
> u-boot-mkimage_2017.03.bb} (100%)
>  rename meta/recipes-bsp/u-boot/{u-boot_2017.01.bb => u-boot_2017.03.bb} 
> (100%)
> 
> diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc 
> b/meta/recipes-bsp/u-boot/u-boot-common_2017.03.inc
> similarity index 86%
> rename from meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc
> rename to meta/recipes-bsp/u-boot/u-boot-common_2017.03.inc
> index df24c853dd..c115f36831 100644
> --- a/meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc
> +++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.03.inc
> @@ -7,7 +7,7 @@ PE = "1"
>  
>  # We use the revision in order to avoid having to fetch it from the
>  # repo during parse
> -SRCREV = "a705ebc81b7f91bbd0ef7c634284208342901149"
> +SRCREV = "8537ddd769f460d7fb7a62a3dcc9669049702e51"
>  
>  SRC_URI = "git://git.denx.de/u-boot.git"
>  
> diff --git a/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.01.bb 
> b/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.03.bb
> similarity index 100%
> rename from meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.01.bb
> rename to meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.03.bb
> diff --git a/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.01.bb 
> b/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.03.bb
> similarity index 100%
> rename from meta/recipes-bsp/u-boot/u-boot-mkimage_2017.01.bb
> rename to meta/recipes-bsp/u-boot/u-boot-mkimage_2017.03.bb
> diff --git a/meta/recipes-bsp/u-boot/u-boot_2017.01.bb 
> b/meta/recipes-bsp/u-boot/u-boot_2017.03.bb
> similarity index 100%
> rename from meta/recipes-bsp/u-boot/u-boot_2017.01.bb
> rename to meta/recipes-bsp/u-boot/u-boot_2017.03.bb
> 
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

[Denys Dmytriyenko]

On Mon, Mar 27, 2017 at 04:52:33PM +0100, Burton, Ross wrote:
> On 27 March 2017 at 16:47, Denys Dmytriyenko  wrote:
> 
> > I haven't personally tested 2017.03 yet, as we are staying on 2017.01 for a
> > bit longer...
> >
> 
> It that just because you've stabilised, or is there something in .03 that
> you're concerned about?

No, I'm not aware of any major issues with .03, although haven't done much 
testing with it due to pending internal release with .01 - the timing is 
rather unfortunate...

-- 
Denys
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

[Denys Dmytriyenko]

On Mon, Mar 27, 2017 at 02:19:56PM +0100, Burton, Ross wrote:
> On 26 March 2017 at 22:14, Denys Dmytriyenko  wrote:
> 
> > At least 2 typos in the description...
> >
> 
> Typos aside, this is past the M3 deadline but RC2 is running late, is there
> a good reason to have the upgrade in?
> 
> Also what boards has it been tested on?  As it's from Otavio I presume the
> Freescale boards have been tested.  Denys, have you tested this version on
> your boards?

Ross,

I haven't personally tested 2017.03 yet, as we are staying on 2017.01 for a 
bit longer...

-- 
Denys
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

[Otavio Salvador]

On Mon, Mar 27, 2017 at 10:19 AM, Burton, Ross  wrote:
...
> Also what boards has it been tested on?  As it's from Otavio I presume the
> Freescale boards have been tested.  Denys, have you tested this version on
> your boards?

We are using it internally and we will upgrade meta-freescale for this
release as well. I believe it would be great to upgrade this as U-Boot
bieng up to date allows for a more up to date reference code.

If there is any failure in the automated tests I can try to iron them
out but I believe it should be fine.

-- 
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

[Burton, Ross]

On 26 March 2017 at 22:14, Denys Dmytriyenko  wrote:

> At least 2 typos in the description...
>

Typos aside, this is past the M3 deadline but RC2 is running late, is there
a good reason to have the upgrade in?

Also what boards has it been tested on?  As it's from Otavio I presume the
Freescale boards have been tested.  Denys, have you tested this version on
your boards?

Cheers
Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

[Otavio Salvador]

On Sun, Mar 26, 2017 at 6:14 PM, Denys Dmytriyenko  wrote:
> On Sun, Mar 26, 2017 at 05:08:13PM -0300, Otavio Salvador wrote:
>> Ths 2017.03 release is out since March 13th 2017 and is the latest
>> stable release prior Pyro release.
>
> At least 2 typos in the description...

Sent a v2.

-- 
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] u-boot: Update to 2017.03 release

[Denys Dmytriyenko]

On Sun, Mar 26, 2017 at 05:08:13PM -0300, Otavio Salvador wrote:
> Ths 2017.03 release is out since March 13th 2017 and is the latest
> stable release prior Pyro release.

At least 2 typos in the description...


> Signed-off-by: Otavio Salvador 
> ---
> 
>  .../u-boot/{u-boot-common_2017.01.inc => u-boot-common_2017.03.inc} | 2 
> +-
>  .../u-boot/{u-boot-fw-utils_2017.01.bb => u-boot-fw-utils_2017.03.bb}   | 0
>  .../u-boot/{u-boot-mkimage_2017.01.bb => u-boot-mkimage_2017.03.bb} | 0
>  meta/recipes-bsp/u-boot/{u-boot_2017.01.bb => u-boot_2017.03.bb}| 0
>  4 files changed, 1 insertion(+), 1 deletion(-)
>  rename meta/recipes-bsp/u-boot/{u-boot-common_2017.01.inc => 
> u-boot-common_2017.03.inc} (86%)
>  rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.01.bb => 
> u-boot-fw-utils_2017.03.bb} (100%)
>  rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.01.bb => 
> u-boot-mkimage_2017.03.bb} (100%)
>  rename meta/recipes-bsp/u-boot/{u-boot_2017.01.bb => u-boot_2017.03.bb} 
> (100%)
> 
> diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc 
> b/meta/recipes-bsp/u-boot/u-boot-common_2017.03.inc
> similarity index 86%
> rename from meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc
> rename to meta/recipes-bsp/u-boot/u-boot-common_2017.03.inc
> index df24c853dd..c115f36831 100644
> --- a/meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc
> +++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.03.inc
> @@ -7,7 +7,7 @@ PE = "1"
>  
>  # We use the revision in order to avoid having to fetch it from the
>  # repo during parse
> -SRCREV = "a705ebc81b7f91bbd0ef7c634284208342901149"
> +SRCREV = "8537ddd769f460d7fb7a62a3dcc9669049702e51"
>  
>  SRC_URI = "git://git.denx.de/u-boot.git"
>  
> diff --git a/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.01.bb 
> b/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.03.bb
> similarity index 100%
> rename from meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.01.bb
> rename to meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.03.bb
> diff --git a/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.01.bb 
> b/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.03.bb
> similarity index 100%
> rename from meta/recipes-bsp/u-boot/u-boot-mkimage_2017.01.bb
> rename to meta/recipes-bsp/u-boot/u-boot-mkimage_2017.03.bb
> diff --git a/meta/recipes-bsp/u-boot/u-boot_2017.01.bb 
> b/meta/recipes-bsp/u-boot/u-boot_2017.03.bb
> similarity index 100%
> rename from meta/recipes-bsp/u-boot/u-boot_2017.01.bb
> rename to meta/recipes-bsp/u-boot/u-boot_2017.03.bb
> -- 
> 2.12.1
> 
> -- 
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core