From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Add support for TechNexion edm1-cf-imx6 SoM
Date: Mon, 04 Nov 2013 10:37:45 -0700 [thread overview]
Message-ID: <5277DB69.3040303@boundarydevices.com> (raw)
In-Reply-To: <CAOMZO5CjZykyvXH+jQCfxiMYxh00R=aFT4Zr+UnjxkibhtfF1A@mail.gmail.com>
On 11/04/2013 10:28 AM, Fabio Estevam wrote:
> Hi Tapani,
>
> On Tue, Sep 10, 2013 at 11:47 AM, Stefano Babic <sbabic@denx.de> wrote:
>>> We are worried that we might not familiar enough with u-boot development to get
>>> such changes accepted in reasonable time.
>>
>> I do not know what you mean for a reasonable time. Merge window is
>> closed, that is patchsets adding new features will not be merged in the
>> next release 2013.10. The next release should be 2013.01, and there are
>> chances to get them merged.
>
> Do you plan to send a new version of the patch that adds support for
> booting a single binary on the mx6q/dl/solo?
>
BTW, I have updated patches to consolidate the IOMUX registers, and
they include updates to board/freescale/titanium.
Should I re-base them on top of the patches which move titanium into
board/barco?
It seems that this change is likely to be applied once Stefano waits
the requisite 48 hours...
Please advise,
Eric
next prev parent reply other threads:[~2013-11-04 17:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 11:23 [U-Boot] [PATCH] Add support for TechNexion edm1-cf-imx6 SoM Tapani
2013-08-28 14:26 ` Eric Bénard
2013-08-30 5:16 ` Tapani Utriainen
2013-08-28 16:08 ` Stefano Babic
2013-08-30 5:07 ` Tapani Utriainen
2013-08-30 13:52 ` Eric Nelson
2013-08-30 14:43 ` Stefano Babic
2013-09-04 11:21 ` Tapani
2013-09-10 14:47 ` Stefano Babic
2013-11-04 17:28 ` Fabio Estevam
2013-11-04 17:37 ` Eric Nelson [this message]
2013-11-04 17:39 ` Otavio Salvador
2013-11-04 17:50 ` Stefano Babic
2013-11-05 15:12 ` Tapani
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=5277DB69.3040303@boundarydevices.com \
--to=eric.nelson@boundarydevices.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox