public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [OE-core] [PATCH] u-boot: Upgrade to 2017.11 release
Date: Fri, 17 Nov 2017 15:59:18 -0500	[thread overview]
Message-ID: <20171117205918.GX9986@bill-the-cat> (raw)
In-Reply-To: <c19104c9-f988-d406-650e-2c9d7d74babd@denx.de>

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.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171117/b50116fd/attachment.sig>

  reply	other threads:[~2017-11-17 20:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14 18:32 [U-Boot] [PATCH] u-boot: Upgrade to 2017.11 release Otavio Salvador
2017-11-15  3:38 ` [U-Boot] [OE-core] " Tom Rini
2017-11-15 16:47 ` Stefan Agner
2017-11-16  8:12   ` Marek Vasut
2017-11-16 12:02     ` Otavio Salvador
2017-11-16 18:21       ` Marek Vasut
2017-11-16 18:34         ` Otavio Salvador
2017-11-16 20:50           ` Ladislav Michl
2017-11-16 22:04             ` Jeroen Hofstee
2017-11-17 19:19 ` [U-Boot] " Marek Vasut
2017-11-17 20:59   ` Tom Rini [this message]
2017-11-18 10:19     ` [U-Boot] [OE-core] " Marek Vasut
2017-11-18 14:14       ` Tom Rini
2017-11-18 19:29         ` Marek Vasut
2017-11-19 14:14           ` Tom Rini

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=20171117205918.GX9986@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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