From: "Burton, Ross" <ross.burton@intel.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.05 release
Date: Wed, 16 May 2018 23:49:09 +0100 [thread overview]
Message-ID: <CAJTo0LZqvWUgL1vj0dn7Ez0YUoS6iwG-bPEp5+gkopnDtitcKA@mail.gmail.com> (raw)
In-Reply-To: <d2492e4a-0dab-21fc-8502-6bc1e19a34f3@denx.de>
I was informed yesterday that AUH had just started, so you should be
getting an email shortly...
On 16 May 2018 at 23:37, Marek Vasut <marex@denx.de> wrote:
> On 05/17/2018 12:00 AM, Otavio Salvador wrote:
>> On Wed, May 16, 2018 at 5:14 PM, Marek Vasut <marex@denx.de> wrote:
>>> This upgrades the U-Boot from 2018.03 to 2018.05 release.
>>>
>>> Signed-off-by: Marek Vasut <marex@denx.de>
>>> Cc: Otavio Salvador <otavio@ossystems.com.br>
>>> Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
>>> Cc: Ross Burton <ross.burton@intel.com>
>>
>> Nice work :-)
>
> Except this kind of patch could (read should) be generated automatically
> by the OE recipe auto-upgrade drone.
>
> --
> Best regards,
> Marek Vasut
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2018-05-16 22:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 20:14 [PATCH] u-boot: Upgrade to 2018.05 release Marek Vasut
2018-05-16 22:00 ` Otavio Salvador
2018-05-16 22:05 ` Khem Raj
2018-05-16 22:12 ` Marek Vasut
2018-05-16 22:37 ` Marek Vasut
2018-05-16 22:49 ` Burton, Ross [this message]
2018-05-16 22:50 ` 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=CAJTo0LZqvWUgL1vj0dn7Ez0YUoS6iwG-bPEp5+gkopnDtitcKA@mail.gmail.com \
--to=ross.burton@intel.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 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.