From: Thierry Reding <treding@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/8] Tegra124: Add arch-tegra124 include/header files
Date: Tue, 8 Oct 2013 09:14:22 +0200 [thread overview]
Message-ID: <20131008071422.GA1734@ulmo.nvidia.com> (raw)
In-Reply-To: <1381185778-25722-1-git-send-email-twarren@nvidia.com>
On Tue, Oct 08, 2013 at 12:42:51AM +0200, Tom Warren wrote:
> No real HW change on T124 for 90% of the toys, so just include
> a common T1x4 header file (based on T114 headers), and if a new
> register/bit is needed, add it at the end. Some headers (clk_rst,
> clock-tables, pinmux, etc.) had too many changes in structs,
> devices, etc. added/removed, so they are added as complete new
> files for T124, and can be diffed against T114 headers to see
> what's changed (again, not a lot).
>
> In a future (RSN) patch I'll point the T114 headers at the
> new common tegra1x4-xxx files, too.
>
> Change-Id: I02a37e1a6bee0c62721f1ffb3968379b36d0f2dd
As a general note: you should strip these Change-Id tags when posting
patches upstream. It's completely useless unless you provide a URL and
access to the gerrit instance that carries the change.
Thierry
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20131008/2a7cf455/attachment.pgp>
next prev parent reply other threads:[~2013-10-08 7:14 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
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 ` Thierry Reding [this message]
2013-10-08 21:29 ` [U-Boot] [PATCH 1/8] Tegra124: Add arch-tegra124 include/header files 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=20131008071422.GA1734@ulmo.nvidia.com \
--to=treding@nvidia.com \
--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;
as well as URLs for NNTP newsgroup(s).