From: Stephen Warren <swarren@nvidia.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Vinod Koul <vinod.koul@intel.com>, Dan Williams <djbw@fb.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dma: tegra: remove useless include of <mach/*.h>
Date: Tue, 28 Aug 2012 10:21:41 -0700 [thread overview]
Message-ID: <503CFE25.2070109@nvidia.com> (raw)
In-Reply-To: <1346137305-7226-1-git-send-email-swarren@wwwdotorg.org>
On 08/28/2012 12:01 AM, Stephen Warren wrote:
> From: Stephen Warren <swarren@nvidia.com>
>
> Nothing from this file is needed, so remove the include. This helps
> single zImage work by reducing use of the mach-tegra/include/mach/
> directory.
BTW, it'd be easiest for me to take this through the Tegra tree, so it
can be consolidated with other header re-org changes.
next prev parent reply other threads:[~2012-08-28 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-28 7:01 [PATCH] dma: tegra: remove useless include of <mach/*.h> Stephen Warren
2012-08-28 17:21 ` Stephen Warren [this message]
2012-08-28 19:10 ` Vinod Koul
2012-09-04 22:24 ` 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=503CFE25.2070109@nvidia.com \
--to=swarren@nvidia.com \
--cc=djbw@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=vinod.koul@intel.com \
/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