From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/7] ARM: mxs: Add SPI clock into clk framwork
Date: Tue, 26 Jun 2012 14:31:10 +0200 [thread overview]
Message-ID: <201206261431.10782.marex@denx.de> (raw)
In-Reply-To: <20120626122424.GG8858@S2101-09.ap.freescale.net>
Dear Shawn Guo,
> On Tue, Jun 26, 2012 at 02:16:11PM +0200, Marek Vasut wrote:
> > So why are those imx28-mmc there ? Shall these not be removed then ?
>
> They are still needed by those non-DT board files. Once we have those
> board files removed, these imx28-mmc lookups will not be needed any
> longer.
Ah ok, I'll discard this patch then.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-06-26 12:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-23 18:43 [PATCH 1/7] ARM: mxs: Move SSP register definitions into separate file Marek Vasut
2012-06-23 18:43 ` [PATCH 2/7] ARM: mxs: Rename IMX2[38]_MMC to IMX2[38]_SSP Marek Vasut
2012-06-23 18:43 ` [PATCH 3/7] ARM: mxs: Add necessary bits into mxs-spi.h Marek Vasut
2012-06-23 18:43 ` [PATCH 4/7] ARM: mxs: Add SPI clock into clk framwork Marek Vasut
2012-06-26 6:54 ` Shawn Guo
2012-06-26 12:16 ` Marek Vasut
2012-06-26 12:24 ` Shawn Guo
2012-06-26 12:31 ` Marek Vasut [this message]
2012-06-23 18:43 ` [PATCH 5/7] ARM: mxs: Pull out parts shared between MMC and SPI Marek Vasut
2012-06-23 18:43 ` [PATCH 6/7] ARM: mxs: Pull out the SSP clock configuration function Marek Vasut
2012-06-23 18:43 ` [PATCH 7/7] ARM: mxs: Add SPI driver for mx233/mx28 Marek Vasut
2012-06-25 13:22 ` Fabio Estevam
2012-06-25 13:30 ` Marek Vasut
2012-06-26 7:43 ` Shawn Guo
2012-06-26 12:22 ` Marek Vasut
2012-06-26 12:31 ` Shawn Guo
2012-06-26 12:50 ` Marek Vasut
2012-06-26 6:52 ` [PATCH 1/7] ARM: mxs: Move SSP register definitions into separate file Shawn Guo
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=201206261431.10782.marex@denx.de \
--to=marex@denx.de \
--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).