On 11/21/2012 08:03 AM, Olof Johansson : > Hi, > > > On Tue, Nov 20, 2012 at 09:59:27AM +0100, Nicolas Ferre wrote: >> Arnd, Olof, >> >> Just for the record, I do not want to put pressure at a such late time in >> the 3.7-rc process. So, I just reworked that pull-request because the previous >> one was wrong: >> - wrong patch content (DT nodes with wrong size) >> - not all tags in patches (Jean-Christophe and Arnd tags were missing...) >> >> Just to start from a sane base if I have to rebase this work for 3.8, I let you know >> that I have updated this tag... >> >> The following changes since commit 641f3ce64b050961d454a0716bb6dbf528315aac: >> >> ARM: at91/usbh: fix overcurrent gpio setup (2012-11-16 10:46:29 +0100) >> >> are available in the git repository at: >> >> git://github.com/at91linux/linux-at91.git tags/at91-fixes > > The new patches seem to belong in an at91/dt branch, not in a fixes one. > > I can pull in the previous fixes branch as an at91/fixes-non-critical for 3.8 > if you want. There's no need to rebase them for this, is there? What is the > pinctrl dependency that you are talking about, are some of these patches needed > as prerequisites for pinctrl changes or the other way around? > > Sorry if I've missed more elaborate emails on this and are asking repeat > questions. ;) No worries Olof, I might have been more precise in the subject of my email: I have made up my mind and consider this material for 3.8. As for the relation with pinctrl, we have made big modification to the layout of some dtsi/dts there and it would make everyones' life easier if we queue these dt/mmc changes on top of the current pinctrl tree... Moreover, Jean-Christophe plans to add the pinctrl part of these additions on top of the modification present in this pull-request: one more reason to queue them in pinctrl git tree. So, in brief: forget this pull-request (and the one that it replaces obviously). Thanks, bye, -- Nicolas Ferre -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
