From: Kishon Vijay Abraham I <kishon@ti.com>
To: "santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com>,
Santosh Shilimkar <ssantosh@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH 0/3] K2G: mmc: Update mmc dt node to use sdhci-omap
Date: Fri, 4 May 2018 13:36:06 +0530 [thread overview]
Message-ID: <e4b70bab-d3bd-7071-aefa-2934c20a3e30@ti.com> (raw)
In-Reply-To: <de0bd46a-21d4-14de-9695-9b0f3996dacb@oracle.com>
Hi Santosh,
On Friday 04 May 2018 12:22 AM, santosh.shilimkar@oracle.com wrote:
> On 5/3/18 4:57 AM, Kishon Vijay Abraham I wrote:
>> Hi Santosh,
>>
>> On Wednesday 25 April 2018 11:10 PM, Santosh Shilimkar wrote:
>>> On 4/25/2018 6:27 AM, Kishon Vijay Abraham I wrote:
>>>> Update mmc dt node to use sdhci-omap binding instead of omap_hsmmc
>>>> binding.
>>>>
>>>> I've also updated keystone_defconfig to enable CONFIG_MMC_SDHCI_OMAP.
>>>> Everyone who use a custom .config should also enable
>>>> CONFIG_MMC_SDHCI_OMAP for MMC to work.
>>>>
>>>> This series should be merged only after [1]
>>>> [1] -> https://marc.info/?l=linux-kernel&m=152465820531802&w=2
>>>>
>>> Keep me posted once the dependency gets merged.
>>
>> Ulf has merged the sdhci part and has shared an immutable branch
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git sdhci_omap
>> with his signed tag sdhci-omap-v4.17-rc3.
>>
>> Can you use it as a base for merging this series?
>>
> How about I apply only DTS patches and exlude config file update ?
> You can send the config patch after the merge window. Are the DTS
> changes also going to break anything without basing of this sdhci
> branch ?
Yes, the bindings has changed for sdhci-omap.
It should also be fine if this entire series can be merged during the 4.18 -rc
cycle since the dependent patches would have been already merged then.
Thanks
Kishon
next prev parent reply other threads:[~2018-05-04 8:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 13:27 [PATCH 0/3] K2G: mmc: Update mmc dt node to use sdhci-omap Kishon Vijay Abraham I
2018-04-25 13:27 ` [PATCH 1/3] ARM: dts: keystone-k2g-evm: Add "vqmmc-supply" property for mmc0/mmc1 Kishon Vijay Abraham I
2018-04-25 13:27 ` [PATCH 2/3] ARM: dts: keystone-k2g-evm: Use sdhci-omap programming model Kishon Vijay Abraham I
2018-04-25 13:27 ` [PATCH 3/3] ARM: configs: keystone: Enable CONFIG_MMC_SDHCI_OMAP Kishon Vijay Abraham I
2018-04-25 17:40 ` [PATCH 0/3] K2G: mmc: Update mmc dt node to use sdhci-omap Santosh Shilimkar
2018-04-26 5:42 ` Kishon Vijay Abraham I
2018-05-03 11:57 ` Kishon Vijay Abraham I
2018-05-03 18:52 ` santosh.shilimkar
2018-05-04 8:06 ` Kishon Vijay Abraham I [this message]
2018-05-04 15:46 ` santosh.shilimkar
2018-06-22 10:12 ` Kishon Vijay Abraham I
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=e4b70bab-d3bd-7071-aefa-2934c20a3e30@ti.com \
--to=kishon@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=santosh.shilimkar@oracle.com \
--cc=ssantosh@kernel.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).