Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751261AbaK1C2z (ORCPT ); Thu, 27 Nov 2014 21:28:55 -0500 Received: from mail-oi0-f43.google.com ([209.85.218.43]:60421 "EHLO mail-oi0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751046AbaK1C2x (ORCPT ); Thu, 27 Nov 2014 21:28:53 -0500 MIME-Version: 1.0 In-Reply-To: <20141127140803.GA3342@developer> References: <1417024212-1775-1-git-send-email-edubezval@gmail.com> <20141127140803.GA3342@developer> Date: Fri, 28 Nov 2014 07:58:52 +0530 Message-ID: Subject: Re: [PATCH 1/1] thermal: cpu_cooling: check for the readiness of cpufreq layer From: Viresh Kumar To: Eduardo Valentin Cc: Linux PM , Lukasz Majewski , LKML , "devicetree@vger.kernel.org" , Grant Likely , Kukjin Kim , "linux-arm-kernel@lists.infradead.org" , linux-samsung-soc , Naveen Krishna Chatradhi , Rob Herring , Zhang Rui Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 27 November 2014 at 19:38, Eduardo Valentin wrote: >> Acked-by: Viresh Kumar > > Ok. > > though.. "normal practice" says ack's are oftern used by the maintainer > of the affected code (quoting Documentation/SubmittingPatches) :-) Hehe :) Another paragraph from the same file: Acked-by: does not necessarily indicate acknowledgement of the entire patch. For example, if a patch affects multiple subsystems and has an Acked-by: from one subsystem maintainer then this usually indicates acknowledgement of just the part which affects that maintainer's code. Judgement should be used here. When in doubt people should refer to the original discussion in the mailing list archives. So my Acked-by was as cpufreq subsystem Maintainer :) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/