On 03-07-15, 14:57, Daniel Lezcano wrote:
Hi Viresh,
all the patches applied to my branch.
the subject format changed. It is under the form: clockevents/drivers/<mydriver>: subject You don't have to worry about that, I did the changes.
There was a conflict for the exynos_mct driver. I fixed it.
Thanks a lot..
- In the future, could please send smaller patch series, so I can
review them more easily and take the entire feature piece by piece. That will make things smoother instead of having to take a day to process the changes.
I know it got a bit longer this time as there were lots of drivers in clocksource directory and I sent them all together.
What about this, following are the patches left with me now:
Group 1: ARM: timer-sp: Migrate to new 'set-state' interface ARM: smp_twd: Migrate to new 'set-state' interface ARM: cns3xxx: Migrate to new 'set-state' interface ARM: davinci: Migrate to new 'set-state' interface ARM: footbridge: Migrate to new 'set-state' interface ARM: gemini: Migrate to new 'set-state' interface ARM: imx: Migrate to new 'set-state' interface ARM: ixp4xx: Migrate to new 'set-state' interface ARM: ks8695: Migrate to new 'set-state' interface ARM: lpc32xx: Migrate to new 'set-state' interface ARM: mmp: Migrate to new 'set-state' interface ARM: netx: Migrate to new 'set-state' interface ARM: omap: Migrate to new 'set-state' interface ARM: SPEAr: Migrate to new 'set-state' interface ARM: w90x900: Migrate to new 'set-state' interface ARM: iop: Migrate to new 'set-state' interface ARM: orion: Migrate to new 'set-state' interface
Group 2: MIPS: alchemy: Migrate to new 'set-state' interface MIPS: jazz: Migrate to new 'set-state' interface MIPS: jz4740: Migrate to new 'set-state' interface MIPS: cevt-bcm1480: Migrate to new 'set-state' interface MIPS: cevt-ds1287: Migrate to new 'set-state' interface MIPS: cevt-gt641xx: Migrate to new 'set-state' interface MIPS: cevt-r4k: Migrate to new 'set-state' interface MIPS: cevt-rsb1250: Migrate to new 'set-state' interface MIPS: cevt-txx9: Migrate to new 'set-state' interface MIPS: loongson: Migrate to new 'set-state' interface MIPS: loongsoon1: Migrate to new 'set-state' interface MIPS: ralink: Migrate to new 'set-state' interface MIPS: sgi-ip27: Migrate to new 'set-state' interface MIPS: sni: Migrate to new 'set-state' interface
Group 3: x86: apic: Migrate to new 'set-state' interface x86: hpet: Migrate to new 'set-state' interface x86: lguest: Migrate to new 'set-state' interface x86: uv: Migrate to new 'set-state' interface x86: xen: Migrate to new 'set-state' interface
Group 4: alpha: Migrate to new 'set-state' interface ARC: Migrate to new 'set-state' interface AVR32: Migrate to new 'set-state' interface blackfin: Migrate to new 'set-state' interface c6x: Migrate to new 'set-state' interface cris: Migrate to new 'set-state' interface hexagon: Migrate to new 'set-state' interface m68k: Migrate to new 'set-state' interface microblaze: Migrate to new 'set-state' interface mn10300: Migrate to new 'set-state' interface nios2: Migrate to new 'set-state' interface openrisc: Migrate to new 'set-state' interface powerpc: Migrate to new 'set-state' interface s390: Migrate to new 'set-state' interface score: Migrate to new 'set-state' interface sh: Migrate to new 'set-state' interface sparc: Migrate to new 'set-state' interface tile: Migrate to new 'set-state' interface um: Migrate to new 'set-state' interface unicore: Migrate to new 'set-state' interface xtensa: Migrate to new 'set-state' interface hv: Migrate to new 'set-state' interface time: broadcast-hrtimer: Migrate to new 'set-state' interface
Will it be fine to send patches in above groups now ? I may send them on the same day, but these will be present in four different patchsets.
I am also not sure about the Maintainership aspect of path above patches would be touching. Will they go through your tree? If not, then how will we fix the dependency on
352370adb058 ("clockevents: Allow set-state callbacks to be optional")
If all clockevent drivers go through you and Thomas, then it would be much easier. Otherwise we may need to push above patch early, so that other maintainers can apply these patches directly over mainline.