From: Preeti U Murthy <preeti@linux.vnet.ibm.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: stewart@linux.vnet.ibm.com, linux-pm@vger.kernel.org,
rafael.j.wysocki@intel.com, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH V4] cpuidle/powernv: Read target_residency value of idle states from DT if available
Date: Wed, 18 Feb 2015 11:48:23 +0530 [thread overview]
Message-ID: <54E42EAF.1080609@linux.vnet.ibm.com> (raw)
In-Reply-To: <3335960.mm4nUDCbyI@vostro.rjw.lan>
On 02/18/2015 11:21 AM, Rafael J. Wysocki wrote:
> On Wednesday, February 18, 2015 10:13:23 AM Preeti U Murthy wrote:
>>
>> On 02/17/2015 11:23 PM, Rafael J. Wysocki wrote:
>>> On Tuesday, February 17, 2015 01:29:10 PM Preeti U Murthy wrote:
>>>> Hi Rafael,
>>>
>>> Hi,
>>>
>>>> Can you please pull this patch ?
>>>
>>> Sorry, I wasn't sure whether or not the patch was for me to take and then
>>> I've been traveling lately. Applied now.
>>
>> Hi Rafael,
>>
>> I saw that the kbuild bot reported build issues around pr_warn() in this patch.
>> I have fixed this and below is the corrected patch. Do let me know if I have
>> to send it out as a separate version/RESEND tag.
>
> I've applied it, thanks!
>
>>>> Another patch based on top of this is waiting to be pulled:
>>>> [PATCH] driver/cpuidle-powernv: Avoid endianness conversions while parsing DT
>>>
>>> OK, have you posted it already?
>> Yes I have. https://lkml.org/lkml/2015/2/3/24.
>
> OK, so this one does not apply for me on top of the other. Can you rebase it
> on top of my current linux-next branch and resend it, please?
>
> Also I'd appreciate it if someone could ACK DT-related stuff for me.
Yes Ill get this done.
>
>> This patch is also waiting to be pulled by you. There was some confusion
>> around who should pull this, but since it all the code is in the driver, we
>> thought it would be best if you pulled it.
>
> Well, OK. If you want me to apply a patch, send it To: me and not To: someone
> else. If you send it To: someone else, I'll ignore it.
>
> Also ask people to review and ACK things you want me to pull, especially if
> that's not stuff I'm particularly familiar with (like related to DT bindings
> specific to your platform etc.).
>
Sure Ill do that. Thanks!
Regards
Preeti U Murthy
>
WARNING: multiple messages have this Message-ID (diff)
From: Preeti U Murthy <preeti@linux.vnet.ibm.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: stewart@linux.vnet.ibm.com, rafael.j.wysocki@intel.com,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH V4] cpuidle/powernv: Read target_residency value of idle states from DT if available
Date: Wed, 18 Feb 2015 11:48:23 +0530 [thread overview]
Message-ID: <54E42EAF.1080609@linux.vnet.ibm.com> (raw)
In-Reply-To: <3335960.mm4nUDCbyI@vostro.rjw.lan>
On 02/18/2015 11:21 AM, Rafael J. Wysocki wrote:
> On Wednesday, February 18, 2015 10:13:23 AM Preeti U Murthy wrote:
>>
>> On 02/17/2015 11:23 PM, Rafael J. Wysocki wrote:
>>> On Tuesday, February 17, 2015 01:29:10 PM Preeti U Murthy wrote:
>>>> Hi Rafael,
>>>
>>> Hi,
>>>
>>>> Can you please pull this patch ?
>>>
>>> Sorry, I wasn't sure whether or not the patch was for me to take and then
>>> I've been traveling lately. Applied now.
>>
>> Hi Rafael,
>>
>> I saw that the kbuild bot reported build issues around pr_warn() in this patch.
>> I have fixed this and below is the corrected patch. Do let me know if I have
>> to send it out as a separate version/RESEND tag.
>
> I've applied it, thanks!
>
>>>> Another patch based on top of this is waiting to be pulled:
>>>> [PATCH] driver/cpuidle-powernv: Avoid endianness conversions while parsing DT
>>>
>>> OK, have you posted it already?
>> Yes I have. https://lkml.org/lkml/2015/2/3/24.
>
> OK, so this one does not apply for me on top of the other. Can you rebase it
> on top of my current linux-next branch and resend it, please?
>
> Also I'd appreciate it if someone could ACK DT-related stuff for me.
Yes Ill get this done.
>
>> This patch is also waiting to be pulled by you. There was some confusion
>> around who should pull this, but since it all the code is in the driver, we
>> thought it would be best if you pulled it.
>
> Well, OK. If you want me to apply a patch, send it To: me and not To: someone
> else. If you send it To: someone else, I'll ignore it.
>
> Also ask people to review and ACK things you want me to pull, especially if
> that's not stuff I'm particularly familiar with (like related to DT bindings
> specific to your platform etc.).
>
Sure Ill do that. Thanks!
Regards
Preeti U Murthy
>
next prev parent reply other threads:[~2015-02-18 6:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 6:20 [PATCH V4] cpuidle/powernv: Read target_residency value of idle states from DT if available Preeti U Murthy
2015-02-17 7:59 ` Preeti U Murthy
2015-02-17 17:53 ` Rafael J. Wysocki
2015-02-17 17:53 ` Rafael J. Wysocki
2015-02-18 4:43 ` Preeti U Murthy
2015-02-18 4:43 ` Preeti U Murthy
2015-02-18 5:51 ` Rafael J. Wysocki
2015-02-18 5:51 ` Rafael J. Wysocki
2015-02-18 6:18 ` Preeti U Murthy [this message]
2015-02-18 6:18 ` Preeti U Murthy
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=54E42EAF.1080609@linux.vnet.ibm.com \
--to=preeti@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=stewart@linux.vnet.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.