Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: buildroot@busybox.net
Subject: [Buildroot] Re-post: Freescale i.MX updates
Date: Wed, 12 Feb 2014 10:43:43 -0700	[thread overview]
Message-ID: <52FBB2CF.10705@boundarydevices.com> (raw)
In-Reply-To: <52E548F3.5000605@boundarydevices.com>

Hi all,

On 01/26/2014 10:42 AM, Eric Nelson wrote:
> Hi Thomas and Arnout,
>
> I think these two patches got lost during the flurry of activity
> back in October:
>      http://patchwork.ozlabs.org/patch/281707/
>      http://patchwork.ozlabs.org/patch/281706/
>
> I think I covered Arnout's concerns from the V3 patch set:
>      http://patchwork.ozlabs.org/patch/280900/
>
> Let me know if you need anything. The patches apply
> on the current head.
>

Here's my best (and only) Ben Stein impression:

	Anyone, anyone?

Buildroot is now several versions behind with i.MX
releases.

Please advise,


Eric

  reply	other threads:[~2014-02-12 17:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-26 17:42 [Buildroot] Freescale i.MX updates Eric Nelson
2014-02-12 17:43 ` Eric Nelson [this message]
2014-02-12 19:34   ` [Buildroot] Re-post: " Peter Korsgaard
2014-02-12 20:03     ` Eric Nelson

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=52FBB2CF.10705@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --cc=buildroot@busybox.net \
    /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