From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] u-boot: Upgrade to 2017.09
Date: Wed, 13 Sep 2017 22:20:18 +0200 [thread overview]
Message-ID: <e1470e87-bf69-850e-5666-eba2f4faedf9@gmail.com> (raw)
In-Reply-To: <CAP9ODKpmqtGUt7jiqww6=9QcN_0Ou2Dc+THAqbYH6F-KsW45YQ@mail.gmail.com>
On 09/13/2017 10:11 PM, Otavio Salvador wrote:
> On Wed, Sep 13, 2017 at 5:05 PM, Marek Vasut <marek.vasut@gmail.com> wrote:
> ...
>> What is the status of those dangling patches ? They were apparently
>> posted, but didn't make it into the last two (?) releases.
>
> I am confused. Are you asking for U-Boot community or OE community?
How does that matter ? I am asking about the status of those patches and
why they didn't make it upstream yet. Something should be done about that.
Automated update of the U-Boot recipe version is great and all, but
that's not all that should be done when new version is released . The
outstanding patches need to be rechecked every now and then too so they
get upstream and don't start piling up in OE core.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2017-09-13 20:20 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 20:30 [PATCH] u-boot: Upgrade to 2017.09 Otavio Salvador
2017-09-11 20:30 ` [U-Boot] " Otavio Salvador
2017-09-13 20:05 ` Marek Vasut
2017-09-13 20:11 ` Otavio Salvador
2017-09-13 20:11 ` Otavio Salvador
2017-09-13 20:20 ` Marek Vasut [this message]
2017-09-13 21:02 ` Otavio Salvador
2017-09-13 21:02 ` Otavio Salvador
2017-09-13 21:23 ` Marek Vasut
2017-09-17 9:18 ` Martin Jansa
2017-09-17 9:18 ` [U-Boot] [OE-core] " Martin Jansa
2017-09-17 11:06 ` Martin Jansa
2017-09-17 11:06 ` [U-Boot] [OE-core] " Martin Jansa
2017-09-18 5:32 ` Marek Vasut
2017-09-18 7:54 ` [U-Boot] " Martin Jansa
2017-09-18 7:54 ` [U-Boot] [OE-core] " Martin Jansa
2017-09-18 8:31 ` Marek Vasut
2017-09-18 8:39 ` [U-Boot] " Martin Jansa
2017-09-18 8:39 ` [U-Boot] [OE-core] " Martin Jansa
2017-09-18 15:20 ` [U-Boot] " Philip Balister
2017-09-18 15:20 ` [U-Boot] [OE-core] " Philip Balister
2017-09-18 15:46 ` [U-Boot] " Otavio Salvador
2017-09-18 15:46 ` [U-Boot] [OE-core] " Otavio Salvador
2017-09-18 15:51 ` [U-Boot] " Burton, Ross
2017-09-18 15:51 ` [U-Boot] [OE-core] " Burton, Ross
2017-09-18 16:06 ` [U-Boot] " Tom Rini
2017-09-18 16:06 ` [U-Boot] [OE-core] " Tom Rini
2017-09-19 8:15 ` [U-Boot] " Marek Vasut
2017-09-19 8:15 ` [U-Boot] [OE-core] " Marek Vasut
2017-09-21 21:35 ` [U-Boot] " Philip Balister
2017-09-21 21:35 ` [U-Boot] [OE-core] " Philip Balister
2017-09-22 22:19 ` [U-Boot] " Marek Vasut
2017-09-22 22:19 ` [U-Boot] [OE-core] " Marek Vasut
2017-09-22 22:22 ` [U-Boot] " Moritz Fischer
2017-09-22 22:22 ` [U-Boot] [OE-core] " Moritz Fischer
2017-09-22 23:36 ` [U-Boot] " Martin Jansa
2017-09-22 23:36 ` [U-Boot] [OE-core] " Martin Jansa
2017-09-22 23:44 ` [U-Boot] " Marek Vasut
2017-09-22 23:44 ` [U-Boot] [OE-core] " Marek Vasut
2017-09-17 15:35 ` Khem Raj
2017-09-17 15:35 ` [U-Boot] [OE-core] " Khem Raj
2017-09-18 8:39 ` Łukasz Majewski
2017-09-19 2:11 ` Randy MacLeod
2017-09-19 2:11 ` [U-Boot] [OE-core] " Randy MacLeod
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=e1470e87-bf69-850e-5666-eba2f4faedf9@gmail.com \
--to=marek.vasut@gmail.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 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.