On Thu, Jan 14, 2016 at 11:09:47AM +0100, Geert Uytterhoeven wrote: > Hi Vinod, > > On Mon, Nov 16, 2015 at 4:55 AM, Vinod Koul <vinod.koul@xxxxxxxxx> wrote: > > On Thu, Nov 12, 2015 at 10:53:59AM +0900, Simon Horman wrote: > >> In general Renesas hardware is not documented to the extent where the > >> relationship between IP blocks on different SoCs can be assumed although > >> they may appear to operate the same way. Furthermore the documentation > >> typically does not specify a version for individual IP blocks. For these > >> reasons a convention of using the SoC name in place of a version and > >> providing SoC-specific compat strings has been adopted. > >> > >> Although not universally liked this convention is used in the bindings for > >> most drivers for Renesas hardware. The purpose of this patch is to > >> update the Renesas R-Car DMA Controller driver to follow this convention. > > > > Applied, thanks > > This patch (and this patch only) has disappeared from your next branch between > January 6 and 7, and thus wasn't included in your pull request for v4.5. > > Was there a specific reason for that, or was it just an oversight? > > Note that the added compatible values in in use (in arm-soc/for-next). Hi Geert, That only means I messed up. I apply patches to for-linus or topic branches and then merge all topics to for-linus and send that to Linus. In this case I didn't see this in any of the topics or for-linus which means I applied to next which I usually trash and keep rebuiling on latest -rc. Now git helped me track this commit on a deleted branch (which reminds us what a wonderful thing git is... screwed up, dont worrry git is our superhero to rescue). I have cherry-picked this patch and applied to for-4.5 branch and will send to Linus in few days along with few more fixes. Thanks for reporting -- ~Vinod -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
