From: konkers@google.com (Erik Gilling)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC/PATCH 00/10] Tegra2 support
Date: Thu, 18 Mar 2010 13:30:45 -0700 [thread overview]
Message-ID: <4344f3c71003181330v3c548182u411dd8eaf9fd34b7@mail.gmail.com> (raw)
In-Reply-To: <20100318083220.GA8267@n2100.arm.linux.org.uk>
On Thu, Mar 18, 2010 at 1:32 AM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> On Mon, Mar 15, 2010 at 11:41:18PM -0700, konkers at google.com wrote:
>> Here's the cleaned up patch stack as promised. ?We've incorporated the feedback
>> from Gary and Russel.
>>
>> I've pushed these patches to the linux-tegra-2.6.34-rc1 branch at
>> git://android.git.kernel.org/kernel/tegra.git
>
> Please change all the mach/io.h and asm/io.h to linux/io.h, and mach/gpio.h
> and asm/gpio.h to linux/gpio.h.
I assume I want to use asm/io.h in entry-macro.S and debug-macro.S, yes?
-Erik
next prev parent reply other threads:[~2010-03-18 20:30 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 16:38 [RFC/PATCH] ARM: add Tegra support Mike Rapoport
2010-03-14 6:51 ` Mike Rapoport
2010-03-15 6:54 ` Thierry Reding
2010-03-15 16:16 ` Thierry Reding
2010-03-15 17:41 ` Gary King
2010-03-15 18:09 ` Russell King - ARM Linux
2010-03-15 22:38 ` Erik Gilling
2010-03-16 6:41 ` [RFC/PATCH 00/10] Tegra2 support konkers at google.com
2010-03-16 6:41 ` [RFC/PATCH 01/10] [ARM] tegra: initial tegra support konkers at google.com
2010-03-16 6:41 ` [RFC/PATCH 02/10] [ARM] tegra: Add IRQ support konkers at google.com
2010-03-16 6:41 ` [RFC/PATCH 03/10] [ARM] tegra: Add clock support konkers at google.com
2010-03-16 6:41 ` [RFC/PATCH 04/10] [ARM] tegra: SMP support konkers at google.com
2010-03-16 6:41 ` [RFC/PATCH 05/10] [ARM] tegra: Add timer support konkers at google.com
2010-03-16 6:41 ` [RFC/PATCH 06/10] [ARM] tegra: add GPIO support konkers at google.com
2010-03-16 6:41 ` [RFC/PATCH 07/10] [ARM] tegra: add pinmux support konkers at google.com
2010-03-16 6:41 ` [RFC/PATCH 08/10] [ARM] tegra: Add framebuffer driver konkers at google.com
2010-03-16 6:41 ` [RFC/PATCH 09/10] [ARM] tegra: harmony: Add harmony board file konkers at google.com
2010-03-16 6:41 ` [RFC/PATCH 10/10] [ARM] tegra: Add harmony_defconfig konkers at google.com
2010-03-17 8:21 ` [RFC/PATCH 09/10] [ARM] tegra: harmony: Add harmony board file Mike Rapoport
2010-03-18 2:27 ` Erik Gilling
2010-03-18 20:41 ` mike at compulab.co.il
2010-03-16 7:57 ` [RFC/PATCH 08/10] [ARM] tegra: Add framebuffer driver Jaya Kumar
2010-03-17 0:31 ` Colin Cross
2010-03-18 8:47 ` Russell King - ARM Linux
2010-03-18 23:57 ` Colin Cross
2010-03-17 8:15 ` [RFC/PATCH 06/10] [ARM] tegra: add GPIO support Mike Rapoport
2010-03-18 2:19 ` Erik Gilling
2010-03-18 8:42 ` [RFC/PATCH 03/10] [ARM] tegra: Add clock support Russell King - ARM Linux
2010-03-18 23:57 ` Colin Cross
2010-03-17 7:57 ` [RFC/PATCH 01/10] [ARM] tegra: initial tegra support Mike Rapoport
2010-03-18 8:32 ` [RFC/PATCH 00/10] Tegra2 support Russell King - ARM Linux
2010-03-18 16:40 ` Erik Gilling
2010-03-18 20:30 ` Erik Gilling [this message]
2010-03-18 21:03 ` Erik Gilling
2010-03-16 8:49 ` [RFC/PATCH] ARM: add Tegra support Mike Rapoport
2010-03-16 13:44 ` Brian Swetland
2010-03-16 14:11 ` Mike Rapoport
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=4344f3c71003181330v3c548182u411dd8eaf9fd34b7@mail.gmail.com \
--to=konkers@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).