linux-kernel - Re: [PATCH V4] cpuidle/powernv: Read target_residency value of idle states from DT if available

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 18 Feb 2015 06:51:12 +0100
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Preeti U Murthy <preeti@...ux.vnet.ibm.com>
Cc:	stewart@...ux.vnet.ibm.com, linux-pm@...r.kernel.org,
	rafael.j.wysocki@...el.com, linux-kernel@...r.kernel.org,
	linuxppc-dev@...ts.ozlabs.org,
	Michael Ellerman <mpe@...erman.id.au>
Subject: Re: [PATCH V4] cpuidle/powernv: Read target_residency value of idle states from DT if available

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.

> 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.).


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/