All of lore.kernel.org
 help / color / mirror / Atom feed
From: "JC" <jc@vtkloud.com>
To: "Fabio Estevam" <festevam@gmail.com>
Cc: meta-freescale@yoctoproject.org,
	Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: Variscite eval Board
Date: Mon, 05 Aug 2013 11:47:06 -0700 (PDT)	[thread overview]
Message-ID: <1375728425202.c71c6191@Nodemailer> (raw)
In-Reply-To: <CAOMZO5CRpR+B9=MSd0gBc-jSPbbEmO7C5oLqRO9imLWrr2aGWA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 694 bytes --]

I'd love it but as I said its out of my skills area:( the initial thread was about asking why I couldn't boot and Otavio offered to have a look to Variscite's patch
I can't tell which policy Variscite will follow about their patches...


Regards
JC


—
JC

On Mon, Aug 5, 2013 at 8:44 PM, Fabio Estevam <festevam@gmail.com> wrote:

> Hi Jean-Charles,
> On Mon, Aug 5, 2013 at 3:33 PM, Jean-Charles JC Verdié <jc@vtkloud.com> wrote:
>> Here's the link: https://dl.dropboxusercontent.com/u/15843/variscite%20patches.zip
> Why not simply add the support of this board to upstream U-boot?
> We should avoid keep maintaining old versions of U-boot.
> Regards,
> Fabio Estevam

[-- Attachment #2: Type: text/html, Size: 1095 bytes --]

  reply	other threads:[~2013-08-05 18:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-03 23:10 Variscite eval Board JC
2013-08-04 19:03 ` Otavio Salvador
2013-08-04 20:35   ` JC
2013-08-04 20:41     ` Otavio Salvador
2013-08-05 16:55       ` Jean-Charles JC Verdié
2013-08-05 17:07         ` Otavio Salvador
2013-08-05 18:33           ` Jean-Charles JC Verdié
2013-08-05 18:44             ` Fabio Estevam
2013-08-05 18:47               ` JC [this message]
2013-08-06 15:11                 ` Otavio Salvador
2013-08-06 15:13                   ` Otavio Salvador
2013-08-06 15:17                     ` Jean-Charles JC Verdié
2013-08-06 16:23                       ` 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=1375728425202.c71c6191@Nodemailer \
    --to=jc@vtkloud.com \
    --cc=festevam@gmail.com \
    --cc=meta-freescale@yoctoproject.org \
    --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.