From: Chris Ball <chris@printf.net>
To: Dinh Nguyen <dinh.linux@gmail.com>
Cc: Seungwon Jeon <tgih.jun@samsung.com>,
dinguyen@altera.com, linux-mmc@vger.kernel.org,
devicetree@vger.kernel.org, 'Rob Herring' <robh+dt@kernel.org>,
'Pawel Moll' <pawel.moll@arm.com>,
'Mark Rutland' <mark.rutland@arm.com>,
'Ian Campbell' <ijc+devicetree@hellion.org.uk>,
'Kumar Gala' <galak@codeaurora.org>,
'Jaehoon Chung' <jh80.chung@samsung.com>
Subject: Re: [PATCHv3 1/3] mmc: dw_mmc-socfpga: Remove the SOCFPGA specific platform for dw_mmc
Date: Thu, 27 Feb 2014 02:32:14 +0000 [thread overview]
Message-ID: <864n3ls2tt.fsf@void.printf.net> (raw)
In-Reply-To: <530CCBBB.9010503@gmail.com> (Dinh Nguyen's message of "Tue, 25 Feb 2014 10:58:35 -0600")
Hi,
On Tue, Feb 25 2014, Dinh Nguyen wrote:
>>> From: Dinh Nguyen <dinguyen@altera.com>
>>>
>>> It turns now that the only really platform specific code that is needed for
>>> SOCFPGA is using the SDMMC_CMD_USE_HOLD_REG in the prepare_command function.
>>> Since the Rockchip already has this functionality, re-use the code that is
>>> already in dw_mmc-pltfm.c.
>>
>> Acked-by: Seungwon Jeon <tgih.jun@samsung.com>
>
> If you're ok with this patch series, can you please apply them for 3.15?
Thanks, pushed to mmc-next for 3.15.
- Chris.
--
Chris Ball <chris@printf.net> <http://printf.net/>
prev parent reply other threads:[~2014-02-27 2:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 2:31 [PATCHv3 1/3] mmc: dw_mmc-socfpga: Remove the SOCFPGA specific platform for dw_mmc dinguyen
2014-02-18 2:31 ` [PATCHv3 2/3] mmc: dw_mmc: Add support for SOCFPGA's platform specific implementation dinguyen
2014-02-18 14:02 ` Seungwon Jeon
2014-02-18 2:31 ` [PATCHv3 3/3] dts: socfpga: Add support for SD/MMC on the SOCFPGA platform dinguyen
2014-02-18 14:09 ` [PATCHv3 1/3] mmc: dw_mmc-socfpga: Remove the SOCFPGA specific platform for dw_mmc Seungwon Jeon
2014-02-25 16:58 ` Dinh Nguyen
2014-02-27 2:32 ` Chris Ball [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=864n3ls2tt.fsf@void.printf.net \
--to=chris@printf.net \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@altera.com \
--cc=dinh.linux@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jh80.chung@samsung.com \
--cc=linux-mmc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=tgih.jun@samsung.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.