Message ID | CAEPRUYqUNxOT=KnhSmbXbL2e2tCs=jAhQqKLiVVc13okpBxHnw@mail.gmail.com |
---|---|
State | New |
Headers | show |
On Tuesday 25 February 2014, Christian Daudt wrote: > Can you please pull the patches below. Note that if you wanto to > absolutely reduce this to the bone, you can drop the last patch in the > series titled "pinctrl: Rename Broadcom Capri pinctrl binding". That > is the documentation fixup, so the binding doc will be wrong until > 3.15. But that will reduce the change to just 2 lines :) I've gone through the remaining pull requests today but didn't touch this one. Since Olof asked for the changes, I'm expecting him to look at the new version first. I don't have an opinion on the contents myself. Arnd
On Tue, Feb 25, 2014 at 08:18:33PM +0100, Arnd Bergmann wrote: > On Tuesday 25 February 2014, Christian Daudt wrote: > > Can you please pull the patches below. Note that if you wanto to > > absolutely reduce this to the bone, you can drop the last patch in the > > series titled "pinctrl: Rename Broadcom Capri pinctrl binding". That > > is the documentation fixup, so the binding doc will be wrong until > > 3.15. But that will reduce the change to just 2 lines :) > > I've gone through the remaining pull requests today but didn't touch > this one. Since Olof asked for the changes, I'm expecting him to > look at the new version first. I don't have an opinion on the contents > myself. Yep, pulled now. I noticed a typo in one of the binding file examples that you might want to fix, but it's not urgent for 3.14: @@ -119,7 +119,7 @@ Optional Properties (for HDMI pins): Example: // pin controller node pinctrl@35004800 { - compatible = "brcm,capri-pinctrl"; + compatible = "brcmbcm11351-pinctrl"; reg = <0x35004800 0x430>; -Olof