From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 1/2] ARM: tegra: move iomap.h to mach-tegra
Date: Mon, 29 Oct 2012 11:04:10 -0600 [thread overview]
Message-ID: <508EB70A.9050605@wwwdotorg.org> (raw)
In-Reply-To: <1350326249-18405-1-git-send-email-swarren@wwwdotorg.org>
On 10/15/2012 12:37 PM, Stephen Warren wrote:
> Nothing outside mach-tegra uses this file, so there's no need for it to
> be in <mach/>.
>
> Since uncompress.h and debug-macro.S remain in include/mach, they need
> to include "../../iomap.h" becaue of this change. uncompress.h will soon
> be deleted in later multi-platform/single-zImage patches. debug-macro.S
> will need to continue to include this header using an explicit relative
> path, to avoid duplicating the physical->virtual address mapping that
> iomap.h dictates.
I have applied this to Tegra's tree for 3.8.
prev parent reply other threads:[~2012-10-29 17:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 18:37 [PATCH 1/2] ARM: tegra: move iomap.h to mach-tegra Stephen Warren
2012-10-15 18:37 ` [PATCH 2/2] ARM: tegra: move irammap.h " Stephen Warren
2012-10-29 17:04 ` Stephen Warren
2012-10-29 17:04 ` 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=508EB70A.9050605@wwwdotorg.org \
--to=swarren@wwwdotorg$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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