linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] OMAP4 coupled CPUidle support for v3.6
Date: Fri, 27 Jul 2012 17:33:37 -0700	[thread overview]
Message-ID: <87pq7ghggu.fsf@ti.com> (raw)
In-Reply-To: <CAOesGMiVRR4F+zad1hKdX-ZuC79U_F5ASG3C52EyFUJpGQv2ow@mail.gmail.com> (Olof Johansson's message of "Fri, 27 Jul 2012 13:22:06 -0700")

Olof Johansson <olof@lixom.net> writes:

> On Thu, Jul 26, 2012 at 11:44 PM, Colin Cross <ccross@android.com> wrote:
>> On Thu, Jul 26, 2012 at 11:34 PM, Shilimkar, Santosh
>> <santosh.shilimkar@ti.com> wrote:
>>> On Fri, Jul 27, 2012 at 2:19 AM, Olof Johansson <olof@lixom.net> wrote:
>>>> Kevin,
>>>>
>>>> On Thu, Jul 26, 2012 at 2:37 PM, Kevin Hilman <khilman@ti.com> 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

      parent reply	other threads:[~2012-07-28  0:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-26 21:37 [GIT PULL] OMAP4 coupled CPUidle support for v3.6 Kevin Hilman
2012-07-27  0:19 ` Olof Johansson
2012-07-27  6:34   ` Shilimkar, Santosh
2012-07-27  6:44     ` Colin Cross
2012-07-27 20:22       ` Olof Johansson
2012-07-27 21:36         ` Shilimkar, Santosh
2012-07-28  0:33         ` Kevin Hilman [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pq7ghggu.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).