From: Tony Lindgren <tony@atomide.com>
To: kishore kadiyala <kishore.kadiyala@ti.com>
Cc: linux-mmc@vger.kernel.org, linux-omap@vger.kernel.org,
madhu.cr@ti.com, jarkko.lavinen@nokia.com, rmk@arm.linux.org.uk,
paul@pwsan.com, santosh.shilimkar@ti.com
Subject: Re: [PATCH v4 0/5] Adding MMC Support on OMAP4430 SDP
Date: Mon, 17 May 2010 19:50:27 -0700 [thread overview]
Message-ID: <20100518025026.GF5818@atomide.com> (raw)
In-Reply-To: <22422.10.24.255.17.1273947606.squirrel@dbdmail.itg.ti.com>
Hi,
* kishore kadiyala <kishore.kadiyala@ti.com> [100515 11:15]:
> Adding MMC1 and MMC2 controllers support for OMAP4
>
> V4:
> - Rebased to "for_next" branch[LO].
> - The first 3 patches [1,2,3] in the series are Minimal set of changes
> with which MMC1/MMC2 works [No card detect for MMC1]on OMAP4 but with
> dependencies on following patches [Not in "for_next" branch]
> [1] I2c patches
> a)https://patchwork.kernel.org/patch/98937/
> b)https://patchwork.kernel.org/patch/98936/
> c)https://patchwork.kernel.org/patch/98939/
> d)https://patchwork.kernel.org/patch/79735/
I've taken the updated versions of the I2C patches,
and fixed them not to break omap3_defconfig.
> [2] Regulator pacth
> a)https://patchwork.kernel.org/patch/94054/
> [3] hsmmc-clk patch
> a)https://patchwork.kernel.org/patch/96821/
I've picked up these too.
> - The patches 4,5 adds card detect feature for MMC1
I only took 1 - 3 out of the MMC patches, it's too
late to start changing the other stuff.
I've reposted the whole series for a quick review.
Regards,
Tony
next prev parent reply other threads:[~2010-05-18 2:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-15 18:20 [PATCH v4 0/5] Adding MMC Support on OMAP4430 SDP kishore kadiyala
2010-05-18 2:50 ` Tony Lindgren [this message]
2010-05-19 0:09 ` Tony Lindgren
2010-05-19 15:25 ` Madhusudhan
2010-05-19 15:44 ` kishore kadiyala
2010-05-20 0:58 ` Tony Lindgren
2010-05-20 5:02 ` Shilimkar, Santosh
2010-05-20 17:31 ` kishore kadiyala
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=20100518025026.GF5818@atomide.com \
--to=tony@atomide.com \
--cc=jarkko.lavinen@nokia.com \
--cc=kishore.kadiyala@ti.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=madhu.cr@ti.com \
--cc=paul@pwsan.com \
--cc=rmk@arm.linux.org.uk \
--cc=santosh.shilimkar@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 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.