From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/2] tegra: clean up board include hell
Date: Mon, 01 Oct 2012 10:24:36 -0600 [thread overview]
Message-ID: <5069C3C4.9080701@wwwdotorg.org> (raw)
In-Reply-To: <1348948929-29928-1-git-send-email-dev@lynxeye.de>
On 09/29/2012 02:02 PM, Lucas Stach wrote:
> The prototypes used in board files were all scattered out, which lead to
> code duplication between SPL and normal U-Boot and some prototypes not actually
> being used. Consolidate this in a common board header.
Seems reasonable enough to me. This series or anything similar that's
also OK with Tom is:
Acked-by: Stephen Warren <swarren@nvidia.com>
next prev parent reply other threads:[~2012-10-01 16:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-29 20:02 [U-Boot] [PATCH v2 1/2] tegra: clean up board include hell Lucas Stach
2012-09-29 20:02 ` [U-Boot] [PATCH v2 2/2] tegra: nand: add board pinmux Lucas Stach
2012-10-04 0:35 ` Simon Glass
2012-10-01 16:24 ` Stephen Warren [this message]
2012-10-01 16:39 ` [U-Boot] [PATCH v2 1/2] tegra: clean up board include hell Tom Warren
2012-10-01 17:12 ` Tom Warren
2012-10-01 17:23 ` Lucas Stach
2012-10-01 20:15 ` Tom Warren
2012-10-02 5:04 ` Simon Glass
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=5069C3C4.9080701@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox