From: Marek Vasut <marex@denx.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: trini@konsulko.com, Otavio Salvador <otavio@ossystems.com.br>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V2] u-boot: Update to 2016.01 release
Date: Thu, 14 Jan 2016 05:41:04 +0100 [thread overview]
Message-ID: <201601140541.04430.marex@denx.de> (raw)
In-Reply-To: <3EB3A651-B3EE-4E31-9A2D-F4D9D71EC4FA@gmail.com>
On Thursday, January 14, 2016 at 05:04:22 AM, Khem Raj wrote:
> > On Jan 13, 2016, at 7:17 PM, Marek Vasut <marex@denx.de> wrote:
> >
> > Upgrade U-Boot to latest version and drop upstreamed patches.
> >
> > 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>
> > ---
> > V2: Drop the _defconfig addition to make ${UBOOT_MACHINE} . This leaves
> >
> > U-Boot build broken unless you abuse the UBOOT_MACHINE variable to
> > explicitly contain the _defconfig bit. Apparently, some BSPs depend
> > on this behavior.
>
> This looks fine now.
Thanks. Are there any further comments down below ?
> > ---
> > ...utils_2015.10.bb => u-boot-fw-utils_2016.01.bb} | 6 +-
> > ...kimage_2015.10.bb => u-boot-mkimage_2016.01.bb} | 6 +-
> > ...-u-boot-.lds-remove-_GLOBAL_OFFSET_TABLE_.patch | 185 ---
> > ...-non-Android-booting-with-ramdisk-and-or-.patch | 36 -
> > ...board_f-enable-setup_board_part1-for-MIPS.patch | 59 -
> > ...PS-bootm-rework-and-fix-broken-bootm-code.patch | 254 -----
> > ...PS-bootm-use-CONFIG_IS_ENABLED-everywhere.patch | 93 --
> > ...-Replace-extern-inline-with-static-inline.patch | 1184
> > -------------------- meta/recipes-bsp/u-boot/u-boot_2015.10.bb
[...]
Best regards,
Marek Vasut
next prev parent reply other threads:[~2016-01-14 4:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 3:17 [PATCH V2] u-boot: Update to 2016.01 release Marek Vasut
2016-01-14 4:04 ` Khem Raj
2016-01-14 4:41 ` Marek Vasut [this message]
2016-01-14 12:18 ` Tom Rini
2016-01-14 20:53 ` 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=201601140541.04430.marex@denx.de \
--to=marex@denx.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=raj.khem@gmail.com \
--cc=trini@konsulko.com \
/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.