From: Marek Vasut <marex@denx.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] u-boot: Factor out common bits
Date: Mon, 5 Sep 2016 21:47:46 +0200 [thread overview]
Message-ID: <1a682b94-a0e2-cc93-92c3-f97e5abf4edd@denx.de> (raw)
In-Reply-To: <1473104036.20226.16.camel@linuxfoundation.org>
On 09/05/2016 09:33 PM, Richard Purdie wrote:
> On Mon, 2016-09-05 at 13:26 -0300, Otavio Salvador wrote:
>> On Mon, Sep 5, 2016 at 1:24 PM, Marek Vasut <marex@denx.de> wrote:
>>>
>>> On 09/05/2016 06:22 PM, Otavio Salvador wrote:
>>>>
>>>> On Mon, Sep 5, 2016 at 1:16 PM, Marek Vasut <marex@denx.de>
>>>> wrote:
>>>> I would love to see the proposed patches.
>>>>
>>> That'd depend on whether they'd be NAK'd right away for breaking
>>> BSPs or
>>> not.
>> It will depends on the type of breakage and the benefits it puts on
>> the table.
>
> I would note that we are past feature freeze at this point and I'm
> struggling to get stability in the patches we have queued without
> anything in addition to that.
>
> If there is a pressing attractive reason we should do this now I'm
> willing to listen but it might be better waiting for 2.3...
Definitely wait for 2.3 with any disruptive changes please.
U-Boot 2016.09 will be out on september 12th, but I don't know if that
can make it into 2.2 release. I can certainly send a patch to update
the recipe.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2016-09-05 19:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 16:21 [PATCH 1/2] u-boot: Factor out common bits Marek Vasut
2016-09-04 16:21 ` [PATCH 2/2] u-boot: Update to 2016.07 release Marek Vasut
2016-09-14 8:48 ` Alexander Kanavin
2016-09-04 21:28 ` [PATCH 1/2] u-boot: Factor out common bits Richard Purdie
2016-09-04 21:49 ` Marek Vasut
2016-09-04 22:11 ` Richard Purdie
2016-09-04 22:23 ` Marek Vasut
2016-09-04 22:33 ` Marek Vasut
2016-09-05 11:02 ` Richard Purdie
2016-09-05 11:04 ` Marek Vasut
2016-09-05 13:51 ` Otavio Salvador
2016-09-05 16:16 ` Marek Vasut
2016-09-05 16:22 ` Otavio Salvador
2016-09-05 16:24 ` Marek Vasut
2016-09-05 16:26 ` Otavio Salvador
2016-09-05 19:33 ` Richard Purdie
2016-09-05 19:47 ` Marek Vasut [this message]
2016-09-05 19:52 ` 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=1a682b94-a0e2-cc93-92c3-f97e5abf4edd@denx.de \
--to=marex@denx.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
--cc=richard.purdie@linuxfoundation.org \
/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.