All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] pull request for u-boot-tegra/master into ARM/master
Date: Tue, 16 Apr 2013 13:55:36 -0600	[thread overview]
Message-ID: <516DACB8.6020502@wwwdotorg.org> (raw)
In-Reply-To: <20130416191726.322ad0c5@lilith>

On 04/16/2013 11:17 AM, Albert ARIBAUD wrote:
> Hi Tom,
> 
> On Mon, 15 Apr 2013 16:28:20 -0700, Tom Warren
> <twarren.nvidia@gmail.com> wrote:
> 
>> Albert,
>>
>> Please pull u-boot-tegra/master into ARM/master. Thanks!
>>
>> ./MAKEALL for all the Tegra boards is OK, running a ./MAKEALL -a arm now.
>> tools/checkpatch.pl is clean.
>>
>> The following changes since commit c4a4e2e20ca226948b62ed116df98f7a3932f2ac:
>>
>>   ARMv7: start.S: stay in HYP mode if u-boot is entered in it (2013-04-15
>> 18:30:59 +0200)
>>
>> are available in the git repository at:
>>
>>   git://git.denx.de/u-boot-tegra master
>>
>> for you to fetch changes up to 601795462a4e7ede97b64dc306de1002e688eef6:
>>
>>   Tegra: T30: Beaver board support. (2013-04-15 16:13:51 -0700)
> 
> +Tom R
> 
> Build-testing done on ARM, all fine ; launching some non-ARM tests just
> in case. In parallel I'm struggling to run-test on TrimSlice as Stephen
> W and Tom W know :), so either someone confirms that ARM ToT does not
> break their own Tegra HW, or my 'applied' will have to wait a couple of
> hours more, until I apply the Trimslice recipe Stephen gave me off-list.

FWIW, I just tested both u-boot-arm/master and u-boot-tegra/master on
TrimSlice and they work fine (well, at least boot to the command-prompt
anyway)

ARM:
c4a4e2e ARMv7: start.S: stay in HYP mode if u-boot is entered in it
Tegra:
6017954 Tegra: T30: Beaver board support.

  reply	other threads:[~2013-04-16 19:55 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15 23:28 [U-Boot] pull request for u-boot-tegra/master into ARM/master Tom Warren
2013-04-16 17:17 ` Albert ARIBAUD
2013-04-16 19:55   ` Stephen Warren [this message]
2013-04-16 20:02     ` Tom Warren
2013-04-17  6:56     ` Albert ARIBAUD
2013-04-16 20:55 ` Albert ARIBAUD
  -- strict thread matches above, loose matches on Subject: below --
2014-08-20 16:12 Tom Warren
2014-08-29 17:48 ` Tom Rini
2014-06-19 17:53 Tom Warren
2014-07-01 16:58 ` Albert ARIBAUD
2014-06-06 15:53 Tom Warren
2014-06-08  7:13 ` Albert ARIBAUD
2014-05-13 21:14 Tom Warren
2014-05-15 16:15 ` Albert ARIBAUD
2014-04-17 16:08 Tom Warren
2014-04-21 19:00 ` Albert ARIBAUD
2014-03-06 15:39 Tom Warren
2014-03-07 14:30 ` Albert ARIBAUD
2014-02-04 23:19 Tom Warren
2014-02-11 16:42 ` Stephen Warren
2014-02-11 16:48   ` Albert ARIBAUD
2014-02-11 16:59     ` Stephen Warren
2014-02-11 17:48       ` Albert ARIBAUD
2014-02-12 17:12 ` Albert ARIBAUD
2013-12-18 20:06 Tom Warren
2013-12-18 21:18 ` Albert ARIBAUD
2013-12-18 22:28   ` Tom Warren
2013-08-19 22:57 Tom Warren
2013-09-04  9:49 ` Albert ARIBAUD
2013-07-11 22:00 Tom Warren
2013-07-12  7:51 ` Albert ARIBAUD
2013-06-06 16:30 Tom Warren
2013-06-07  8:06 ` Albert ARIBAUD
2013-05-28 21:16 Tom Warren
2013-05-29 16:16 ` Albert ARIBAUD
2013-03-25 17:43 Tom Warren
2013-03-26 10:12 ` Albert ARIBAUD
2013-03-15 15:25 Tom Warren
2013-03-15 20:46 ` Albert ARIBAUD
2013-01-18 16:00 Tom Warren
2013-01-18 16:06 ` Albert ARIBAUD
2012-11-16 17:14 Tom Warren
2012-11-16 21:27 ` Albert ARIBAUD
2012-11-16 21:45   ` Tom Warren
2012-11-16 23:33     ` Albert ARIBAUD
2012-11-16 23:42       ` Tom Warren
2012-11-17  0:12         ` Albert ARIBAUD
2012-11-19 15:39           ` Tom Warren
2012-11-19 17:12             ` Tom Warren
2012-11-20  6:21               ` Albert ARIBAUD
2012-10-29 23:49 Tom Warren
2012-11-03  9:03 ` Albert ARIBAUD

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=516DACB8.6020502@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --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 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.