From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mmc: tegra: fix boards that used old CONFIG_TEGRA2_MMC build switch
Date: Fri, 01 Jun 2012 13:00:58 -0600 [thread overview]
Message-ID: <4FC9116A.20509@wwwdotorg.org> (raw)
In-Reply-To: <5FBF8E85CA34454794F0F7ECBA79798F379C4162B2@HQMAIL04.nvidia.com>
On 06/01/2012 12:09 PM, Tom Warren wrote:
> Stephen Warren wrote at Friday, June 01, 2012 10:49 AM:
>> On 06/01/2012 11:11 AM, Tom Warren wrote:
...
>> Grep'ing for the symbols that got renamed in the current u-boot-tegra/next
>> still shows a lot of hits. For MMC those are all include guards so it
>> probably doesn't cause bugs. For SPI, there are some #defines in the driver
>> that didn't get converted.. Should those fixes be included in this patch
>> too?
>
> Current (as of right now) u-boot-tegra/next (which is where this patch lives) doesn't have any instances of CONFIG_TEGRA2_MMC nor CONFIG_TEGRA2_SPI that I can find. Were you using an older /next? All T20 boards build fine from /next w/MAKEALL -s tegra2. I can't test MMC on the Tamonten/Paz00/etc. boards since I don't have any, but I believe I've fixed all the TEGRA2_MMC instances so they should work fine.
Yeah, I guess that's true. I was grep'ing for just TEGRA2_MMC/SPI/GPIO,
not CONFIG_*.
prev parent reply other threads:[~2012-06-01 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 17:11 [U-Boot] [PATCH] mmc: tegra: fix boards that used old CONFIG_TEGRA2_MMC build switch Tom Warren
2012-06-01 17:49 ` Stephen Warren
2012-06-01 18:09 ` Tom Warren
2012-06-01 19:00 ` Stephen Warren [this message]
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=4FC9116A.20509@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.