Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: openembedded-core@lists.openembedded.org
Cc: Marek Vasut <marex@denx.de>, Otavio Salvador <otavio@ossystems.com.br>
Subject: [PATCH] u-boot: Upgrade to 2018.03 release
Date: Mon,  9 Apr 2018 01:02:23 +0200	[thread overview]
Message-ID: <20180408230223.17260-1-marex@denx.de> (raw)

This upgrades the U-Boot from 2018.01 to 2018.03 release and drops
patches accepted upstream, getting the patch count to zero.

Signed-off-by: Marek Vasut <marex@denx.de>
Cc: Otavio Salvador <otavio@ossystems.com.br>
Cc: Ross Burton <ross.burton@intel.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 .../u-boot/files/MPC8315ERDB-enable-DHCP.patch        | 19 -------------------
 ...t-common_2018.01.inc => u-boot-common_2018.03.inc} |  6 ++----
 ...fw-utils_2018.01.bb => u-boot-fw-utils_2018.03.bb} |  0
 ...t-mkimage_2018.01.bb => u-boot-mkimage_2018.03.bb} |  0
 .../u-boot/{u-boot_2018.01.bb => u-boot_2018.03.bb}   |  0
 5 files changed, 2 insertions(+), 23 deletions(-)
 delete mode 100644 meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
 rename meta/recipes-bsp/u-boot/{u-boot-common_2018.01.inc => u-boot-common_2018.03.inc} (68%)
 rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2018.01.bb => u-boot-fw-utils_2018.03.bb} (100%)
 rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2018.01.bb => u-boot-mkimage_2018.03.bb} (100%)
 rename meta/recipes-bsp/u-boot/{u-boot_2018.01.bb => u-boot_2018.03.bb} (100%)

diff --git a/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch b/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
deleted file mode 100644
index ecaa1796a4..0000000000
--- a/meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch
+++ /dev/null
@@ -1,19 +0,0 @@
-Enabled dhcp client functionality for Yocto reference
-hardware MPC8315E-RDB.
-
-Upstream-Status: Pending
-
-Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
-
-Index: git/configs/MPC8315ERDB_defconfig
-===================================================================
---- git.orig/configs/MPC8315ERDB_defconfig
-+++ git/configs/MPC8315ERDB_defconfig
-@@ -12,6 +12,7 @@ CONFIG_CMD_PCI=y
- CONFIG_CMD_SATA=y
- CONFIG_CMD_USB=y
- # CONFIG_CMD_SETEXPR is not set
-+CONFIG_CMD_DHCP=y
- CONFIG_CMD_MII=y
- CONFIG_CMD_PING=y
- CONFIG_CMD_DATE=y
diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2018.01.inc b/meta/recipes-bsp/u-boot/u-boot-common_2018.03.inc
similarity index 68%
rename from meta/recipes-bsp/u-boot/u-boot-common_2018.01.inc
rename to meta/recipes-bsp/u-boot/u-boot-common_2018.03.inc
index d2073ea0c7..8ffae365a9 100644
--- a/meta/recipes-bsp/u-boot/u-boot-common_2018.01.inc
+++ b/meta/recipes-bsp/u-boot/u-boot-common_2018.03.inc
@@ -7,10 +7,8 @@ PE = "1"
 
 # We use the revision in order to avoid having to fetch it from the
 # repo during parse
-SRCREV = "f3dd87e0b98999a78e500e8c6d2b063ebadf535a"
+SRCREV = "f95ab1fb6e37f0601f397091bb011edf7a98b890"
 
-SRC_URI = "git://git.denx.de/u-boot.git \
-    file://MPC8315ERDB-enable-DHCP.patch \
-"
+SRC_URI = "git://git.denx.de/u-boot.git"
 
 S = "${WORKDIR}/git"
diff --git a/meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.01.bb b/meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.03.bb
similarity index 100%
rename from meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.01.bb
rename to meta/recipes-bsp/u-boot/u-boot-fw-utils_2018.03.bb
diff --git a/meta/recipes-bsp/u-boot/u-boot-mkimage_2018.01.bb b/meta/recipes-bsp/u-boot/u-boot-mkimage_2018.03.bb
similarity index 100%
rename from meta/recipes-bsp/u-boot/u-boot-mkimage_2018.01.bb
rename to meta/recipes-bsp/u-boot/u-boot-mkimage_2018.03.bb
diff --git a/meta/recipes-bsp/u-boot/u-boot_2018.01.bb b/meta/recipes-bsp/u-boot/u-boot_2018.03.bb
similarity index 100%
rename from meta/recipes-bsp/u-boot/u-boot_2018.01.bb
rename to meta/recipes-bsp/u-boot/u-boot_2018.03.bb
-- 
2.16.2



             reply	other threads:[~2018-04-08 23:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-08 23:02 Marek Vasut [this message]
2018-04-09  0:54 ` [PATCH] u-boot: Upgrade to 2018.03 release Khem Raj
2018-04-09  7:12   ` Martin Jansa
2018-04-09  8:25   ` Marek Vasut
2018-04-09 13:48     ` Khem Raj
2018-04-09 15:24       ` Marek Vasut
2018-04-10  9:49   ` Martin Hundebøll
2018-04-10  9:55     ` Marek Vasut
     [not found]       ` <d89b39f665a14c63b0821c1ad600da72@SOC-EX01V.e01.socionext.com>
2018-04-11  8:42         ` Martin Hundebøll
     [not found]           ` <32a348ed6176434db8178d29d7e1f183@SOC-EX01V.e01.socionext.com>
2018-04-16  8:40             ` Marek Vasut
2018-04-30 12:17               ` Alexander Kanavin
2018-04-30 17:25                 ` Marek Vasut
2018-04-30 18:05                   ` Martin Hundebøll
2018-04-30 19:46                   ` Alexander Kanavin
2018-04-30 19:57                     ` Otavio Salvador
2018-04-30 20:25                       ` Tom Rini
2018-04-30 20:29                         ` Otavio Salvador
2018-04-30 23:30                           ` Marek Vasut
2018-05-01  0:25                           ` Tom Rini
2018-05-01  1:56                             ` Otavio Salvador
2018-04-11 14:47 ` Burton, Ross
2018-04-11 14:51   ` Marek Vasut
2018-04-21 10:01     ` Robert Berger
2018-04-21 10:52     ` Robert Berger

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=20180408230223.17260-1-marex@denx.de \
    --to=marex@denx.de \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox