public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [STATUS] ARM (Tegra)
Date: Tue, 30 Aug 2011 17:34:47 +0200	[thread overview]
Message-ID: <4E5D0317.4080002@aribaud.net> (raw)
In-Reply-To: <201108301120.40166.vapier@gentoo.org>

Le 30/08/2011 17:20, Mike Frysinger a ?crit :
> On Saturday, August 20, 2011 14:50:27 Mike Frysinger wrote:
>> On Thursday, August 18, 2011 18:09:56 Albert ARIBAUD wrote:
>>> 1) if there are any pull requests to u-voot-arm/master in the works,
>>> please try to submit them soon or at lease let me know, and
>>
>> we've got some Tegra stuff that seems to be waiting for merging (or at
>> least feedback as to anything left that needs to be done so it can be
>> merged): [RESEND PATCH v3 0/4] Add basic clock and pinmux functions to the
>> Tegra2
>>
>> to broach the more general tegra question, should these get sent to Tom and
>> then he sends them to Albert, or should they get sent directly to Albert
>> (since there is no dedicated tegra or nvidia u-boot tree atm) ?  we'd like
>> to get this process smoothed out so we dont keep annoying people :).
>
> ping ...
>
> if people dont care either way, we can just set up a u-boot/u-boot-tegra.git
> tree for Albert to pull from

Seems like people don't care, and I'm fine with applying the patches 
myself, but I don't want to pull from a tree: I'll apply the patches as 
they appear on patchwork.

Are we talking about these four patches?

<http://patchwork.ozlabs.org/patch/110117/>
<http://patchwork.ozlabs.org/patch/110120/>
<http://patchwork.ozlabs.org/patch/110119/>
<http://patchwork.ozlabs.org/patch/110118/>

> -mike

Amicalement,
-- 
Albert.

  reply	other threads:[~2011-08-30 15:34 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-18 22:09 [U-Boot] [STATUS] ARM Albert ARIBAUD
2011-08-19  9:38 ` Aneesh V
2011-08-19 18:19   ` Dirk Behme
2011-08-20 11:12     ` Albert ARIBAUD
2011-08-20 15:32       ` Albert ARIBAUD
2011-08-21  7:11         ` Dirk Behme
2011-08-21  7:22           ` Albert ARIBAUD
2011-08-23  2:02             ` V, Aneesh
2011-08-21  7:46         ` Dirk Behme
2011-08-21  7:54           ` V, Aneesh
2011-08-21  7:51         ` V, Aneesh
2011-08-21  8:14           ` Albert ARIBAUD
2011-08-21  8:56             ` V, Aneesh
2011-08-21 10:13               ` Albert ARIBAUD
2011-08-22  8:15       ` Simon Schwarz
2011-08-23 11:27         ` Michael Jones
2011-08-20 11:16 ` Marek Vasut
2011-08-20 11:44   ` Albert ARIBAUD
2011-08-20 12:24     ` Marek Vasut
2011-08-20 12:54       ` Albert ARIBAUD
2011-08-20 13:33         ` Marek Vasut
2011-08-20 18:50 ` [U-Boot] [STATUS] ARM (Tegra) Mike Frysinger
2011-08-30 15:20   ` Mike Frysinger
2011-08-30 15:34     ` Albert ARIBAUD [this message]
2011-08-30 15:57       ` Simon Glass
2011-08-30 16:27         ` Simon Glass
2011-08-30 16:31         ` Albert ARIBAUD
2011-08-30 16:36           ` Simon Glass
2011-08-30 16:39             ` Albert ARIBAUD
2011-08-30 16:45               ` Simon Glass
2011-08-21 10:17 ` [U-Boot] [STATUS] ARM Dirk Behme
2011-08-30 15:58 ` [U-Boot] [STATUS] ARM status as of 2011-08-30 Albert ARIBAUD
2011-08-30 19:08   ` Wolfgang Denk
2011-08-31 10:25     ` Albert ARIBAUD
2011-08-31 19:55       ` Wolfgang Denk

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=4E5D0317.4080002@aribaud.net \
    --to=albert.u.boot@aribaud.net \
    --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