From mboxrd@z Thu Jan 1 00:00:00 1970 From: khilman@ti.com (Kevin Hilman) Date: Fri, 27 Jul 2012 17:33:37 -0700 Subject: [GIT PULL] OMAP4 coupled CPUidle support for v3.6 In-Reply-To: (Olof Johansson's message of "Fri, 27 Jul 2012 13:22:06 -0700") References: <87394enqz8.fsf@ti.com> Message-ID: <87pq7ghggu.fsf@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Olof Johansson writes: > On Thu, Jul 26, 2012 at 11:44 PM, Colin Cross wrote: >> On Thu, Jul 26, 2012 at 11:34 PM, Shilimkar, Santosh >> wrote: >>> On Fri, Jul 27, 2012 at 2:19 AM, Olof Johansson wrote: >>>> Kevin, >>>> >>>> On Thu, Jul 26, 2012 at 2:37 PM, Kevin Hilman wrote: >>>>> Hi Arnd, Olof, >>>>> >>>>> I know it is late, but I'm really hoping this can still make it for >>>>> v3.6, so consider this a [GIT PLEA]. ;) >>>> >>>> New features submitted halfway through the merge window? Yeah, that's late. >>>> >>>> I'll pull it in as late2/pm once the below is fixed, but I won't >>>> promise we'll send it up. >>>> >>>> >>>>> Kevin Hilman (1): >>>>> ARM: OMAP4: CPUidle: add synchronization for coupled idle states >>>>> >>>>> Santosh Shilimkar (3): >>>>> ARM: OMAP: timer: allow gp timer clock-event to be used on both cpus >>>>> ARM: OMAP4: CPUidle: Use coupled cpuidle states to implement SMP cpuidle. >>>>> ARM: OMAP4: CPUidle: Open broadcast clock-event device. >>>> >>>> This looks odd, Colin was author to the first of the commits >>>> attributed to Santosh. >>>> >>> Not sure what you mean. These patches are written by me. Kevin, Collin helped >>> in review. If you are referring to the {ARM: OMAP: timer: allow gp >>> timer clock-event to be >>> used on both cpus} which does have SOB from me and Colin. The very first version >>> of this version I picked was from product tree in which it was >>> commited on Coiln's name. >>> Later I updated that forf the multi-omap and the new timer code and >>> hence the update >>> in Author. >> >> I have no problem with the authorship on these two patches. > > Santosh, Colin, > > Ok, fair enough -- I just want to make sure attribution happens > appropriately, and it's a red flag when there's a S-o-b by someone not > at your company before yours without explanation. Thanks Olof for considering this very late branch. Kevin