From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 6/8] Tegra124: Add generic T124 build support
Date: Tue, 08 Oct 2013 15:45:16 -0600 [thread overview]
Message-ID: <52547CEC.4090106@wwwdotorg.org> (raw)
In-Reply-To: <1381185778-25722-6-git-send-email-twarren@nvidia.com>
On 10/07/2013 04:42 PM, Tom Warren wrote:
> Basic Tegra124 build support added - no specific
> board is targeted.
The content of this patch seems entirely unrelated to the commit
description.
BTW, if I apply each one of these patches in turn, rather than all of
them at once, can the entire code-base build correctly for all SoCs, or
will I get build errors? I suppose that the boards.cfg is added near the
end of the series, so perhaps there's no issue here.
next prev parent reply other threads:[~2013-10-08 21:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 22:42 [U-Boot] [PATCH 1/8] Tegra124: Add arch-tegra124 include/header files Tom Warren
2013-10-07 22:42 ` [U-Boot] [PATCH 2/8] Tegra124: Add changes to common arch-tegra header files Tom Warren
2013-10-08 7:16 ` Thierry Reding
2013-10-07 22:42 ` [U-Boot] [PATCH 3/8] Tegra124: Add SPL/AVP (arm720t) cpu files Tom Warren
2013-10-08 8:13 ` Thierry Reding
2013-10-08 21:34 ` Stephen Warren
2014-01-22 23:12 ` Stephen Warren
2013-10-08 21:36 ` Stephen Warren
2013-10-07 22:42 ` [U-Boot] [PATCH 4/8] Tegra124: Add CPU (armv7) files Tom Warren
2013-10-07 22:42 ` [U-Boot] [PATCH 5/8] Tegra124: Add common CPU (shared) files Tom Warren
2013-10-08 21:43 ` Stephen Warren
2013-10-07 22:42 ` [U-Boot] [PATCH 6/8] Tegra124: Add generic T124 build support Tom Warren
2013-10-08 21:45 ` Stephen Warren [this message]
2013-10-07 22:42 ` [U-Boot] [PATCH 7/8] Tegra124: Venice2: fdt: Add device-tree files Tom Warren
2013-10-08 21:55 ` Stephen Warren
2013-10-07 22:42 ` [U-Boot] [PATCH 8/8] Tegra124: Add Venice2 (T124) build Tom Warren
2013-10-08 22:06 ` Stephen Warren
2013-10-08 7:14 ` [U-Boot] [PATCH 1/8] Tegra124: Add arch-tegra124 include/header files Thierry Reding
2013-10-08 21:29 ` Stephen Warren
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=52547CEC.4090106@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.