diff mbox series

[U-Boot] u-boot: Upgrade to 2017.11 release

Message ID 20171114183223.7804-1-otavio@ossystems.com.br
State Not Applicable
Delegated to: Tom Rini
Headers show
Series [U-Boot] u-boot: Upgrade to 2017.11 release | expand

Commit Message

Otavio Salvador Nov. 14, 2017, 6:32 p.m. UTC
This upgrades the U-Boot from 2017.09 to 2017.11 release.

Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
---

 .../u-boot/{u-boot-common_2017.09.inc => u-boot-common_2017.11.inc}     | 2 +-
 .../u-boot/{u-boot-fw-utils_2017.09.bb => u-boot-fw-utils_2017.11.bb}   | 0
 .../u-boot/{u-boot-mkimage_2017.09.bb => u-boot-mkimage_2017.11.bb}     | 0
 meta/recipes-bsp/u-boot/{u-boot_2017.09.bb => u-boot_2017.11.bb}        | 0
 4 files changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-bsp/u-boot/{u-boot-common_2017.09.inc => u-boot-common_2017.11.inc} (89%)
 rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.09.bb => u-boot-fw-utils_2017.11.bb} (100%)
 rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.09.bb => u-boot-mkimage_2017.11.bb} (100%)
 rename meta/recipes-bsp/u-boot/{u-boot_2017.09.bb => u-boot_2017.11.bb} (100%)

Comments

Tom Rini Nov. 15, 2017, 3:38 a.m. UTC | #1
On Tue, Nov 14, 2017 at 04:32:23PM -0200, Otavio Salvador wrote:

> This upgrades the U-Boot from 2017.09 to 2017.11 release.
> 
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>

Reviewed-by: Tom Rini <trini@konsulko.com>
Stefan Agner Nov. 15, 2017, 4:47 p.m. UTC | #2
On 2017-11-14 19:32, Otavio Salvador wrote:
> This upgrades the U-Boot from 2017.09 to 2017.11 release.

You might encounter this when building fw_printenv/setenv tools alone:

https://lists.denx.de/pipermail/u-boot/2017-November/311505.html

--
Stefan

> 
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
> 
>  .../u-boot/{u-boot-common_2017.09.inc => u-boot-common_2017.11.inc}     | 2 +-
>  .../u-boot/{u-boot-fw-utils_2017.09.bb => u-boot-fw-utils_2017.11.bb}   | 0
>  .../u-boot/{u-boot-mkimage_2017.09.bb => u-boot-mkimage_2017.11.bb}     | 0
>  meta/recipes-bsp/u-boot/{u-boot_2017.09.bb => u-boot_2017.11.bb}        | 0
>  4 files changed, 1 insertion(+), 1 deletion(-)
>  rename meta/recipes-bsp/u-boot/{u-boot-common_2017.09.inc =>
> u-boot-common_2017.11.inc} (89%)
>  rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.09.bb =>
> u-boot-fw-utils_2017.11.bb} (100%)
>  rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.09.bb =>
> u-boot-mkimage_2017.11.bb} (100%)
>  rename meta/recipes-bsp/u-boot/{u-boot_2017.09.bb => u-boot_2017.11.bb} (100%)
> 
> diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc
> b/meta/recipes-bsp/u-boot/u-boot-common_2017.11.inc
> similarity index 89%
> rename from meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc
> rename to meta/recipes-bsp/u-boot/u-boot-common_2017.11.inc
> index 02e51242cb..bfdf1a0d8f 100644
> --- a/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc
> +++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.11.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 = "c98ac3487e413c71e5d36322ef3324b21c6f60f9"
> +SRCREV = "c253573f3e269fd9a24ee6684d87dd91106018a5"
>  
>  SRC_URI = "git://git.denx.de/u-boot.git \
>      file://MPC8315ERDB-enable-DHCP.patch \
> diff --git a/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.09.bb
> b/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.11.bb
> similarity index 100%
> rename from meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.09.bb
> rename to meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.11.bb
> diff --git a/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.09.bb
> b/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.11.bb
> similarity index 100%
> rename from meta/recipes-bsp/u-boot/u-boot-mkimage_2017.09.bb
> rename to meta/recipes-bsp/u-boot/u-boot-mkimage_2017.11.bb
> diff --git a/meta/recipes-bsp/u-boot/u-boot_2017.09.bb
> b/meta/recipes-bsp/u-boot/u-boot_2017.11.bb
> similarity index 100%
> rename from meta/recipes-bsp/u-boot/u-boot_2017.09.bb
> rename to meta/recipes-bsp/u-boot/u-boot_2017.11.bb
> -- 
> 2.15.0
Marek Vasut Nov. 16, 2017, 8:12 a.m. UTC | #3
On 11/15/2017 05:47 PM, Stefan Agner wrote:
> On 2017-11-14 19:32, Otavio Salvador wrote:
>> This upgrades the U-Boot from 2017.09 to 2017.11 release.
> 
> You might encounter this when building fw_printenv/setenv tools alone:
> 
> https://lists.denx.de/pipermail/u-boot/2017-November/311505.html

[...]

>>  SRC_URI = "git://git.denx.de/u-boot.git \
>>      file://MPC8315ERDB-enable-DHCP.patch \
I also see that the number of out-of-tree patches didn't change since
last time, even though I complained about it ... why are these patches
still here ?
Otavio Salvador Nov. 16, 2017, 12:02 p.m. UTC | #4
On Thu, Nov 16, 2017 at 6:12 AM, Marek Vasut <marex@denx.de> wrote:
> On 11/15/2017 05:47 PM, Stefan Agner wrote:
>> On 2017-11-14 19:32, Otavio Salvador wrote:
>>> This upgrades the U-Boot from 2017.09 to 2017.11 release.
>>
>> You might encounter this when building fw_printenv/setenv tools alone:
>>
>> https://lists.denx.de/pipermail/u-boot/2017-November/311505.html
>
> [...]
>
>>>  SRC_URI = "git://git.denx.de/u-boot.git \
>>>      file://MPC8315ERDB-enable-DHCP.patch \
> I also see that the number of out-of-tree patches didn't change since
> last time, even though I complained about it ... why are these patches
> still here ?

Because you are the maintainer and didn't do your duty. Stop
complaining and go help please.
Marek Vasut Nov. 16, 2017, 6:21 p.m. UTC | #5
On 11/16/2017 01:02 PM, Otavio Salvador wrote:
> On Thu, Nov 16, 2017 at 6:12 AM, Marek Vasut <marex@denx.de> wrote:
>> On 11/15/2017 05:47 PM, Stefan Agner wrote:
>>> On 2017-11-14 19:32, Otavio Salvador wrote:
>>>> This upgrades the U-Boot from 2017.09 to 2017.11 release.
>>>
>>> You might encounter this when building fw_printenv/setenv tools alone:
>>>
>>> https://lists.denx.de/pipermail/u-boot/2017-November/311505.html
>>
>> [...]
>>
>>>>  SRC_URI = "git://git.denx.de/u-boot.git \
>>>>      file://MPC8315ERDB-enable-DHCP.patch \
>> I also see that the number of out-of-tree patches didn't change since
>> last time, even though I complained about it ... why are these patches
>> still here ?
> 
> Because you are the maintainer and didn't do your duty.

And what duty is that exactly ? I at least inquired about the status of
these patches and reviewed them [1] (the other was not submitted to ML
yet and submitter is not responding), so do you have anything else in mind ?

[1] https://marc.info/?l=u-boot&m=150533817907015&w=2

> Stop complaining and go help please.

I'll just ignore this comment, see above.
Otavio Salvador Nov. 16, 2017, 6:34 p.m. UTC | #6
On Thu, Nov 16, 2017 at 4:21 PM, Marek Vasut <marex@denx.de> wrote:
> On 11/16/2017 01:02 PM, Otavio Salvador wrote:
>> On Thu, Nov 16, 2017 at 6:12 AM, Marek Vasut <marex@denx.de> wrote:
>>> On 11/15/2017 05:47 PM, Stefan Agner wrote:
>>>> On 2017-11-14 19:32, Otavio Salvador wrote:
>>>>> This upgrades the U-Boot from 2017.09 to 2017.11 release.
>>>>
>>>> You might encounter this when building fw_printenv/setenv tools alone:
>>>>
>>>> https://lists.denx.de/pipermail/u-boot/2017-November/311505.html
>>>
>>> [...]
>>>
>>>>>  SRC_URI = "git://git.denx.de/u-boot.git \
>>>>>      file://MPC8315ERDB-enable-DHCP.patch \
>>> I also see that the number of out-of-tree patches didn't change since
>>> last time, even though I complained about it ... why are these patches
>>> still here ?
>>
>> Because you are the maintainer and didn't do your duty.
>
> And what duty is that exactly ? I at least inquired about the status of
> these patches and reviewed them [1] (the other was not submitted to ML
> yet and submitter is not responding), so do you have anything else in mind ?
>
> [1] https://marc.info/?l=u-boot&m=150533817907015&w=2

Good, so I don't see the reason for the question.

I did upgrade the recipe and tested. It didn't have patches merged so
there is nothing I can do. You being the maintainer can keep an eye
here.

>>> I also see that the number of out-of-tree patches didn't change since
>>> last time, even though I complained about it ... why are these patches
>>> still here ?

Your question was pointless. So instead of "complain" as you said,
make sure those are merged.
Ladislav Michl Nov. 16, 2017, 8:50 p.m. UTC | #7
On Thu, Nov 16, 2017 at 04:34:51PM -0200, Otavio Salvador wrote:
> On Thu, Nov 16, 2017 at 4:21 PM, Marek Vasut <marex@denx.de> wrote:
> > On 11/16/2017 01:02 PM, Otavio Salvador wrote:
> >> On Thu, Nov 16, 2017 at 6:12 AM, Marek Vasut <marex@denx.de> wrote:
> >>> On 11/15/2017 05:47 PM, Stefan Agner wrote:
> >>>> On 2017-11-14 19:32, Otavio Salvador wrote:
> >>>>> This upgrades the U-Boot from 2017.09 to 2017.11 release.
> >>>>
> >>>> You might encounter this when building fw_printenv/setenv tools alone:
> >>>>
> >>>> https://lists.denx.de/pipermail/u-boot/2017-November/311505.html
> >>>
> >>> [...]
> >>>
> >>>>>  SRC_URI = "git://git.denx.de/u-boot.git \
> >>>>>      file://MPC8315ERDB-enable-DHCP.patch \
> >>> I also see that the number of out-of-tree patches didn't change since
> >>> last time, even though I complained about it ... why are these patches
> >>> still here ?
> >>
> >> Because you are the maintainer and didn't do your duty.
> >
> > And what duty is that exactly ? I at least inquired about the status of
> > these patches and reviewed them [1] (the other was not submitted to ML
> > yet and submitter is not responding), so do you have anything else in mind ?
> >
> > [1] https://marc.info/?l=u-boot&m=150533817907015&w=2
> 
> Good, so I don't see the reason for the question.
> 
> I did upgrade the recipe and tested. It didn't have patches merged so
> there is nothing I can do. 

Sure there is. Merging patches does not happen automagically, so it is
your (or whoevers, but definitely not maintainers) responsibility to check
upstream status and eventually resubmit.

> You being the maintainer can keep an eye here.

No. Maintainer's job is mostly rejecting poor quality patches and merging
those properly submited, tested and described. What you are asking for
is ussually called babysitting.

> >>> I also see that the number of out-of-tree patches didn't change since
> >>> last time, even though I complained about it ... why are these patches
> >>> still here ?
> 
> Your question was pointless. So instead of "complain" as you said,
> make sure those are merged.

While I see no reason U-Boot list was cc'ed on this patch, your attitude
is almost perfect example how _not_ to do opensource development.

Best regards,
	ladis
Jeroen Hofstee Nov. 16, 2017, 10:04 p.m. UTC | #8
Hello Ledislav,

> While I see no reason U-Boot list was cc'ed on this patch, your attitude
> is almost perfect example how _not_ to do opensource development.
>

As an occasional reader, it seems that this is a rather harsh, I am sure 
Marex
and Otavio can handle it themselves..

Regards,
Jeroen
Marek Vasut Nov. 17, 2017, 7:19 p.m. UTC | #9
On 11/14/2017 07:32 PM, Otavio Salvador wrote:
> This upgrades the U-Boot from 2017.09 to 2017.11 release.
> 
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
> 
>  .../u-boot/{u-boot-common_2017.09.inc => u-boot-common_2017.11.inc}     | 2 +-
>  .../u-boot/{u-boot-fw-utils_2017.09.bb => u-boot-fw-utils_2017.11.bb}   | 0
>  .../u-boot/{u-boot-mkimage_2017.09.bb => u-boot-mkimage_2017.11.bb}     | 0
>  meta/recipes-bsp/u-boot/{u-boot_2017.09.bb => u-boot_2017.11.bb}        | 0
>  4 files changed, 1 insertion(+), 1 deletion(-)
>  rename meta/recipes-bsp/u-boot/{u-boot-common_2017.09.inc => u-boot-common_2017.11.inc} (89%)
>  rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.09.bb => u-boot-fw-utils_2017.11.bb} (100%)
>  rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.09.bb => u-boot-mkimage_2017.11.bb} (100%)
>  rename meta/recipes-bsp/u-boot/{u-boot_2017.09.bb => u-boot_2017.11.bb} (100%)
> 
> diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc b/meta/recipes-bsp/u-boot/u-boot-common_2017.11.inc
> similarity index 89%
> rename from meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc
> rename to meta/recipes-bsp/u-boot/u-boot-common_2017.11.inc
> index 02e51242cb..bfdf1a0d8f 100644
> --- a/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc
> +++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.11.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 = "c98ac3487e413c71e5d36322ef3324b21c6f60f9"
> +SRCREV = "c253573f3e269fd9a24ee6684d87dd91106018a5"
>  
>  SRC_URI = "git://git.denx.de/u-boot.git \
>      file://MPC8315ERDB-enable-DHCP.patch \

This patch ^ could use a refresh , since it applies with Fuzz now.

[...]
Tom Rini Nov. 17, 2017, 8:59 p.m. UTC | #10
On Fri, Nov 17, 2017 at 08:19:07PM +0100, Marek Vasut wrote:
> On 11/14/2017 07:32 PM, Otavio Salvador wrote:
> > This upgrades the U-Boot from 2017.09 to 2017.11 release.
> > 
> > Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> > ---
> > 
> >  .../u-boot/{u-boot-common_2017.09.inc => u-boot-common_2017.11.inc}     | 2 +-
> >  .../u-boot/{u-boot-fw-utils_2017.09.bb => u-boot-fw-utils_2017.11.bb}   | 0
> >  .../u-boot/{u-boot-mkimage_2017.09.bb => u-boot-mkimage_2017.11.bb}     | 0
> >  meta/recipes-bsp/u-boot/{u-boot_2017.09.bb => u-boot_2017.11.bb}        | 0
> >  4 files changed, 1 insertion(+), 1 deletion(-)
> >  rename meta/recipes-bsp/u-boot/{u-boot-common_2017.09.inc => u-boot-common_2017.11.inc} (89%)
> >  rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.09.bb => u-boot-fw-utils_2017.11.bb} (100%)
> >  rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.09.bb => u-boot-mkimage_2017.11.bb} (100%)
> >  rename meta/recipes-bsp/u-boot/{u-boot_2017.09.bb => u-boot_2017.11.bb} (100%)
> > 
> > diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc b/meta/recipes-bsp/u-boot/u-boot-common_2017.11.inc
> > similarity index 89%
> > rename from meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc
> > rename to meta/recipes-bsp/u-boot/u-boot-common_2017.11.inc
> > index 02e51242cb..bfdf1a0d8f 100644
> > --- a/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc
> > +++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.11.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 = "c98ac3487e413c71e5d36322ef3324b21c6f60f9"
> > +SRCREV = "c253573f3e269fd9a24ee6684d87dd91106018a5"
> >  
> >  SRC_URI = "git://git.denx.de/u-boot.git \
> >      file://MPC8315ERDB-enable-DHCP.patch \
> 
> This patch ^ could use a refresh , since it applies with Fuzz now.

Honestly, just enable DISTRO_DEFAULTS for the board and post that
upstream instead.
Marek Vasut Nov. 18, 2017, 10:19 a.m. UTC | #11
On 11/17/2017 09:59 PM, Tom Rini wrote:
> On Fri, Nov 17, 2017 at 08:19:07PM +0100, Marek Vasut wrote:
>> On 11/14/2017 07:32 PM, Otavio Salvador wrote:
>>> This upgrades the U-Boot from 2017.09 to 2017.11 release.
>>>
>>> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
>>> ---
>>>
>>>  .../u-boot/{u-boot-common_2017.09.inc => u-boot-common_2017.11.inc}     | 2 +-
>>>  .../u-boot/{u-boot-fw-utils_2017.09.bb => u-boot-fw-utils_2017.11.bb}   | 0
>>>  .../u-boot/{u-boot-mkimage_2017.09.bb => u-boot-mkimage_2017.11.bb}     | 0
>>>  meta/recipes-bsp/u-boot/{u-boot_2017.09.bb => u-boot_2017.11.bb}        | 0
>>>  4 files changed, 1 insertion(+), 1 deletion(-)
>>>  rename meta/recipes-bsp/u-boot/{u-boot-common_2017.09.inc => u-boot-common_2017.11.inc} (89%)
>>>  rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.09.bb => u-boot-fw-utils_2017.11.bb} (100%)
>>>  rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.09.bb => u-boot-mkimage_2017.11.bb} (100%)
>>>  rename meta/recipes-bsp/u-boot/{u-boot_2017.09.bb => u-boot_2017.11.bb} (100%)
>>>
>>> diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc b/meta/recipes-bsp/u-boot/u-boot-common_2017.11.inc
>>> similarity index 89%
>>> rename from meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc
>>> rename to meta/recipes-bsp/u-boot/u-boot-common_2017.11.inc
>>> index 02e51242cb..bfdf1a0d8f 100644
>>> --- a/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc
>>> +++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.11.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 = "c98ac3487e413c71e5d36322ef3324b21c6f60f9"
>>> +SRCREV = "c253573f3e269fd9a24ee6684d87dd91106018a5"
>>>  
>>>  SRC_URI = "git://git.denx.de/u-boot.git \
>>>      file://MPC8315ERDB-enable-DHCP.patch \
>>
>> This patch ^ could use a refresh , since it applies with Fuzz now.
> 
> Honestly, just enable DISTRO_DEFAULTS for the board and post that
> upstream instead.

Or that, but someone would have to test that first and the patch author
does not respond for some reason.
Tom Rini Nov. 18, 2017, 2:14 p.m. UTC | #12
On Sat, Nov 18, 2017 at 11:19:13AM +0100, Marek Vasut wrote:
> On 11/17/2017 09:59 PM, Tom Rini wrote:
> > On Fri, Nov 17, 2017 at 08:19:07PM +0100, Marek Vasut wrote:
> >> On 11/14/2017 07:32 PM, Otavio Salvador wrote:
> >>> This upgrades the U-Boot from 2017.09 to 2017.11 release.
> >>>
> >>> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> >>> ---
> >>>
> >>>  .../u-boot/{u-boot-common_2017.09.inc => u-boot-common_2017.11.inc}     | 2 +-
> >>>  .../u-boot/{u-boot-fw-utils_2017.09.bb => u-boot-fw-utils_2017.11.bb}   | 0
> >>>  .../u-boot/{u-boot-mkimage_2017.09.bb => u-boot-mkimage_2017.11.bb}     | 0
> >>>  meta/recipes-bsp/u-boot/{u-boot_2017.09.bb => u-boot_2017.11.bb}        | 0
> >>>  4 files changed, 1 insertion(+), 1 deletion(-)
> >>>  rename meta/recipes-bsp/u-boot/{u-boot-common_2017.09.inc => u-boot-common_2017.11.inc} (89%)
> >>>  rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.09.bb => u-boot-fw-utils_2017.11.bb} (100%)
> >>>  rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.09.bb => u-boot-mkimage_2017.11.bb} (100%)
> >>>  rename meta/recipes-bsp/u-boot/{u-boot_2017.09.bb => u-boot_2017.11.bb} (100%)
> >>>
> >>> diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc b/meta/recipes-bsp/u-boot/u-boot-common_2017.11.inc
> >>> similarity index 89%
> >>> rename from meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc
> >>> rename to meta/recipes-bsp/u-boot/u-boot-common_2017.11.inc
> >>> index 02e51242cb..bfdf1a0d8f 100644
> >>> --- a/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc
> >>> +++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.11.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 = "c98ac3487e413c71e5d36322ef3324b21c6f60f9"
> >>> +SRCREV = "c253573f3e269fd9a24ee6684d87dd91106018a5"
> >>>  
> >>>  SRC_URI = "git://git.denx.de/u-boot.git \
> >>>      file://MPC8315ERDB-enable-DHCP.patch \
> >>
> >> This patch ^ could use a refresh , since it applies with Fuzz now.
> > 
> > Honestly, just enable DISTRO_DEFAULTS for the board and post that
> > upstream instead.
> 
> Or that, but someone would have to test that first and the patch author
> does not respond for some reason.

Adding in Ed..

Yes, it would be good if the MPC8315 got run-time tested more often, but
no, a build test is sufficient I think for changing a few options like
this.
Marek Vasut Nov. 18, 2017, 7:29 p.m. UTC | #13
On 11/18/2017 03:14 PM, Tom Rini wrote:
> On Sat, Nov 18, 2017 at 11:19:13AM +0100, Marek Vasut wrote:
>> On 11/17/2017 09:59 PM, Tom Rini wrote:
>>> On Fri, Nov 17, 2017 at 08:19:07PM +0100, Marek Vasut wrote:
>>>> On 11/14/2017 07:32 PM, Otavio Salvador wrote:
>>>>> This upgrades the U-Boot from 2017.09 to 2017.11 release.
>>>>>
>>>>> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
>>>>> ---
>>>>>
>>>>>  .../u-boot/{u-boot-common_2017.09.inc => u-boot-common_2017.11.inc}     | 2 +-
>>>>>  .../u-boot/{u-boot-fw-utils_2017.09.bb => u-boot-fw-utils_2017.11.bb}   | 0
>>>>>  .../u-boot/{u-boot-mkimage_2017.09.bb => u-boot-mkimage_2017.11.bb}     | 0
>>>>>  meta/recipes-bsp/u-boot/{u-boot_2017.09.bb => u-boot_2017.11.bb}        | 0
>>>>>  4 files changed, 1 insertion(+), 1 deletion(-)
>>>>>  rename meta/recipes-bsp/u-boot/{u-boot-common_2017.09.inc => u-boot-common_2017.11.inc} (89%)
>>>>>  rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.09.bb => u-boot-fw-utils_2017.11.bb} (100%)
>>>>>  rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.09.bb => u-boot-mkimage_2017.11.bb} (100%)
>>>>>  rename meta/recipes-bsp/u-boot/{u-boot_2017.09.bb => u-boot_2017.11.bb} (100%)
>>>>>
>>>>> diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc b/meta/recipes-bsp/u-boot/u-boot-common_2017.11.inc
>>>>> similarity index 89%
>>>>> rename from meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc
>>>>> rename to meta/recipes-bsp/u-boot/u-boot-common_2017.11.inc
>>>>> index 02e51242cb..bfdf1a0d8f 100644
>>>>> --- a/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc
>>>>> +++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.11.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 = "c98ac3487e413c71e5d36322ef3324b21c6f60f9"
>>>>> +SRCREV = "c253573f3e269fd9a24ee6684d87dd91106018a5"
>>>>>  
>>>>>  SRC_URI = "git://git.denx.de/u-boot.git \
>>>>>      file://MPC8315ERDB-enable-DHCP.patch \
>>>>
>>>> This patch ^ could use a refresh , since it applies with Fuzz now.
>>>
>>> Honestly, just enable DISTRO_DEFAULTS for the board and post that
>>> upstream instead.
>>
>> Or that, but someone would have to test that first and the patch author
>> does not respond for some reason.
> 
> Adding in Ed..
> 
> Yes, it would be good if the MPC8315 got run-time tested more often, but
> no, a build test is sufficient I think for changing a few options like
> this.

I didn't have very good experience with changing such stuff for random
board and not actually testing it thus far ...
Tom Rini Nov. 19, 2017, 2:14 p.m. UTC | #14
On Sat, Nov 18, 2017 at 08:29:36PM +0100, Marek Vasut wrote:
> On 11/18/2017 03:14 PM, Tom Rini wrote:
> > On Sat, Nov 18, 2017 at 11:19:13AM +0100, Marek Vasut wrote:
> >> On 11/17/2017 09:59 PM, Tom Rini wrote:
> >>> On Fri, Nov 17, 2017 at 08:19:07PM +0100, Marek Vasut wrote:
> >>>> On 11/14/2017 07:32 PM, Otavio Salvador wrote:
> >>>>> This upgrades the U-Boot from 2017.09 to 2017.11 release.
> >>>>>
> >>>>> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> >>>>> ---
> >>>>>
> >>>>>  .../u-boot/{u-boot-common_2017.09.inc => u-boot-common_2017.11.inc}     | 2 +-
> >>>>>  .../u-boot/{u-boot-fw-utils_2017.09.bb => u-boot-fw-utils_2017.11.bb}   | 0
> >>>>>  .../u-boot/{u-boot-mkimage_2017.09.bb => u-boot-mkimage_2017.11.bb}     | 0
> >>>>>  meta/recipes-bsp/u-boot/{u-boot_2017.09.bb => u-boot_2017.11.bb}        | 0
> >>>>>  4 files changed, 1 insertion(+), 1 deletion(-)
> >>>>>  rename meta/recipes-bsp/u-boot/{u-boot-common_2017.09.inc => u-boot-common_2017.11.inc} (89%)
> >>>>>  rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.09.bb => u-boot-fw-utils_2017.11.bb} (100%)
> >>>>>  rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.09.bb => u-boot-mkimage_2017.11.bb} (100%)
> >>>>>  rename meta/recipes-bsp/u-boot/{u-boot_2017.09.bb => u-boot_2017.11.bb} (100%)
> >>>>>
> >>>>> diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc b/meta/recipes-bsp/u-boot/u-boot-common_2017.11.inc
> >>>>> similarity index 89%
> >>>>> rename from meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc
> >>>>> rename to meta/recipes-bsp/u-boot/u-boot-common_2017.11.inc
> >>>>> index 02e51242cb..bfdf1a0d8f 100644
> >>>>> --- a/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc
> >>>>> +++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.11.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 = "c98ac3487e413c71e5d36322ef3324b21c6f60f9"
> >>>>> +SRCREV = "c253573f3e269fd9a24ee6684d87dd91106018a5"
> >>>>>  
> >>>>>  SRC_URI = "git://git.denx.de/u-boot.git \
> >>>>>      file://MPC8315ERDB-enable-DHCP.patch \
> >>>>
> >>>> This patch ^ could use a refresh , since it applies with Fuzz now.
> >>>
> >>> Honestly, just enable DISTRO_DEFAULTS for the board and post that
> >>> upstream instead.
> >>
> >> Or that, but someone would have to test that first and the patch author
> >> does not respond for some reason.
> > 
> > Adding in Ed..
> > 
> > Yes, it would be good if the MPC8315 got run-time tested more often, but
> > no, a build test is sufficient I think for changing a few options like
> > this.
> 
> I didn't have very good experience with changing such stuff for random
> board and not actually testing it thus far ...

Since we're just talking about enabling a few more generic commands, I
think you might be being a tad overly cautious here...
diff mbox series

Patch

diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc b/meta/recipes-bsp/u-boot/u-boot-common_2017.11.inc
similarity index 89%
rename from meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc
rename to meta/recipes-bsp/u-boot/u-boot-common_2017.11.inc
index 02e51242cb..bfdf1a0d8f 100644
--- a/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc
+++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.11.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 = "c98ac3487e413c71e5d36322ef3324b21c6f60f9"
+SRCREV = "c253573f3e269fd9a24ee6684d87dd91106018a5"
 
 SRC_URI = "git://git.denx.de/u-boot.git \
     file://MPC8315ERDB-enable-DHCP.patch \
diff --git a/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.09.bb b/meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.11.bb
similarity index 100%
rename from meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.09.bb
rename to meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.11.bb
diff --git a/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.09.bb b/meta/recipes-bsp/u-boot/u-boot-mkimage_2017.11.bb
similarity index 100%
rename from meta/recipes-bsp/u-boot/u-boot-mkimage_2017.09.bb
rename to meta/recipes-bsp/u-boot/u-boot-mkimage_2017.11.bb
diff --git a/meta/recipes-bsp/u-boot/u-boot_2017.09.bb b/meta/recipes-bsp/u-boot/u-boot_2017.11.bb
similarity index 100%
rename from meta/recipes-bsp/u-boot/u-boot_2017.09.bb
rename to meta/recipes-bsp/u-boot/u-boot_2017.11.bb