From: Andrew Morton <akpm@linux-foundation.org>
To: Purushotam Kumar <purushotam@ti.com>
Cc: davinci-linux-open-source@linux.davincidsp.com,
linux-kernel@vger.kernel.org, drzeus-mmc@drzeus.cx,
purushotam@ti.com
Subject: Re: [PATCH 1/1] DaVinci: MMC: Updated MMC/SD controller driver for DaVinci family.
Date: Mon, 30 Mar 2009 14:10:37 -0700 [thread overview]
Message-ID: <20090330141037.f473bf99.akpm@linux-foundation.org> (raw)
In-Reply-To: <1237378885-5918-1-git-send-email-purushotam@ti.com>
On Wed, 18 Mar 2009 17:51:25 +0530
Purushotam Kumar <purushotam@ti.com> wrote:
> This patch adds support for MMC/SD controller driver for DaVinci family SoC.
> This patch will work for SoC like DM6446 and DM355. SoC like DM365 and
> DA830 also has same controller with small variations and could supported/added
> easily by using this version of patch. It means that this version of patch
> could be used for all SoC which has been derived from DaVinci family.
>
> This patch has been generated against latest 2.6.29 mainline kernel. This patch
> will not compile currently because it depends notably on the EDMA utilities and
> chip/board setup, that will come at some point through the ARM tree. Please use
> currently DaVinci GIT tree for EDMA utilities and chip/board setup etc.
The wont-compile thing makes it a bit hard for me to merge.
Specifically where are these prerequisite patches and how will I know
when they are available and in what tree?
Perhaps the simplest approach would be for you to wait until the code
_will_ compile?
prev parent reply other threads:[~2009-03-30 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 12:21 [PATCH 1/1] DaVinci: MMC: Updated MMC/SD controller driver for DaVinci family Purushotam Kumar
2009-03-23 20:17 ` David Brownell
2009-03-24 11:57 ` Kumar, Purushotam
2009-03-30 21:10 ` Andrew Morton [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=20090330141037.f473bf99.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=drzeus-mmc@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=purushotam@ti.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