From: Tom Rini <trini@konsulko.com>
To: Marek Vasut <marex@denx.de>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>,
Otavio Salvador <otavio@ossystems.com.br>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] u-boot: Upgrade to 2018.01 release
Date: Fri, 19 Jan 2018 16:58:33 -0500 [thread overview]
Message-ID: <20180119215833.GA4660@bill-the-cat> (raw)
In-Reply-To: <1518fd89-c875-1ced-aca6-8f4e53f65548@denx.de>
[-- Attachment #1: Type: text/plain, Size: 872 bytes --]
On Fri, Jan 19, 2018 at 10:46:56PM +0100, Marek Vasut wrote:
> On 01/19/2018 07:18 PM, Otavio Salvador wrote:
> > On Fri, Jan 19, 2018 at 3:45 PM, Marek Vasut <marex@denx.de> wrote:
> >> This upgrades the U-Boot from 2017.11 to 2018.01 release
> >> and drops patches accepted upstream.
> >>
> >> Signed-off-by: Marek Vasut <marex@denx.de>
> >
> > Acked-by: Otavio Salvador <otavio@ossystems.com.br>
> >
> > ...
> >> file://MPC8315ERDB-enable-DHCP.patch \
> >
> > Please send this patch for next release so we can drop it as well.
>
> Look up the previous thread on why this patch is still here ...
Yes, and FWIW, I still think it's of the type that's safely merged
upstream. A group of users needs additional generic functionality
enabled on a board. CC the listed maintainer, and York, and I expect it
would come in. Thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2018-01-19 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 17:45 [PATCH] u-boot: Upgrade to 2018.01 release Marek Vasut
2018-01-19 18:18 ` Otavio Salvador
2018-01-19 21:46 ` Marek Vasut
2018-01-19 21:58 ` Tom Rini [this message]
2018-01-19 22:21 ` Marek Vasut
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=20180119215833.GA4660@bill-the-cat \
--to=trini@konsulko.com \
--cc=marex@denx.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
--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