Message ID | CAOh2x==Dh5thHoQaQ+eN34oeWsmZ32kMOOQ6nU5kO7Tfcr=PUA@mail.gmail.com |
---|---|
State | New |
Headers | show |
On Monday 30 April 2012, viresh kumar wrote: > Hi Arnd/Olof, > > This is pull request for SPEAr13xx support updates. It had dependency > on for-v3.5-spear-clk, spear/dt and spear/pinctrl for applying patches, and > so i created a merge of v3.4-rc5 with spear/dt and pinctrl branches and applied > for-v3.5-spear-clk patches, before this patchset. > > Also, it has compilation dependencies with: > - Mike's clk-next branch > - Russell's: CLKDEV: Add helper routines to allocate and add clkdevs for ... Ok, I missed the compilation dependencies you mentioned here. So the branch you sent me doesn't actually build by itself, which is not good. I have now merged both as staging branches, which means it will be in linux-next from now on but can still get rebased in order to work out the dependencies. We can work out something from here once I understand where the dependencies are. Arnd
On 4/30/2012 11:16 PM, Arnd Bergmann wrote: > Ok, I missed the compilation dependencies you mentioned here. So the branch > you sent me doesn't actually build by itself, which is not good. I thought, i must not add patches from Russell and Mike in my pull request, as they haven't made to linux-next till now. i.e. even if this branch doesn't compile by itself, it should get compiled when it is merged with your branch, where these dependencies must be present already. Isn't this the right approach? > I have now merged both as staging branches, which means it will be in linux-next > from now on but can still get rebased in order to work out the dependencies. Ok. > We can work out something from here once I understand where the dependencies > are. These two only: - Mike's clk-next branch - Russell's: CLKDEV: Add helper routines to allocate and add clkdevs for ...
On Tuesday 01 May 2012, Viresh Kumar wrote: > > On 4/30/2012 11:16 PM, Arnd Bergmann wrote: > > Ok, I missed the compilation dependencies you mentioned here. So the branch > > you sent me doesn't actually build by itself, which is not good. > > I thought, i must not add patches from Russell and Mike in my pull request, as they > haven't made to linux-next till now. i.e. even if this branch doesn't compile by > itself, it should get compiled when it is merged with your branch, where these > dependencies must be present already. Isn't this the right approach? It's more complicated than this. You are right that you cannot just add patches to one tree that should go through a different tree. However, another requirement is that all branches are bisectable and you have a working kernel at each intermediate step. It takes some experience to get it all working. > > We can work out something from here once I understand where the dependencies > > are. > > These two only: > > - Mike's clk-next branch The right solution for this would have been to take it as another base merged with the other two branches and put the new patches on top, and then let me pull in the clk-next branch as a dependency into linux-next that needs to get upstream first before I send out your patches. This is not as important for a new platform like spear13xx because there won't be any regressions, but you should absolutely make sure that you don't break existing platforms. I also noticed now that the pinctrl patches in the spear3xx series don't work by themselves and have another dependency on the stuff that I presume is in Linus' pinctrl tree. > - Russell's: CLKDEV: Add helper routines to allocate and add clkdevs for ... I could not find out the status of that patch. Which branch is it going to get merged through? Arnd
On 5/1/2012 2:04 PM, Arnd Bergmann wrote: > I could not find out the status of that patch. Which branch is it going to get > merged through? Russell has floated the last version of this one himself. Maybe he will take it through his tree only.
On Tue, May 01, 2012 at 08:34:14AM +0000, Arnd Bergmann wrote: > On Tuesday 01 May 2012, Viresh Kumar wrote: > > - Russell's: CLKDEV: Add helper routines to allocate and add clkdevs for ... > > I could not find out the status of that patch. Which branch is it going to get > merged through? That's because I've not committed it yet.
On Tue, May 01, 2012 at 09:38:13AM +0100, Russell King - ARM Linux wrote: > On Tue, May 01, 2012 at 08:34:14AM +0000, Arnd Bergmann wrote: > > On Tuesday 01 May 2012, Viresh Kumar wrote: > > > - Russell's: CLKDEV: Add helper routines to allocate and add clkdevs for ... > > > > I could not find out the status of that patch. Which branch is it going to get > > merged through? > > That's because I've not committed it yet. Note also that the latest version of it, posted just last Saturday, has yet to attract any replies what so ever.
On Tuesday 01 May 2012, Russell King - ARM Linux wrote: > On Tue, May 01, 2012 at 09:38:13AM +0100, Russell King - ARM Linux wrote: > > On Tue, May 01, 2012 at 08:34:14AM +0000, Arnd Bergmann wrote: > > > On Tuesday 01 May 2012, Viresh Kumar wrote: > > > > - Russell's: CLKDEV: Add helper routines to allocate and add clkdevs for ... > > > > > > I could not find out the status of that patch. Which branch is it going to get > > > merged through? > > > > That's because I've not committed it yet. > > Note also that the latest version of it, posted just last Saturday, has > yet to attract any replies what so ever. Ok. In that case, we need to wait until that is settled and applied to a stable branch. Viresh, please tell me when all the dependencies are merged somewhere, then we can do a refresh of your patches on top of those. You can either send me a new version then, or I can rebased the patches from the staging branch and apply them into a proper next/* branch. Arnd