[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAKohpok90KG7ZcY8qq7g-VmhPSCsn83Ut_K_QJqC2b+efWiXkg@mail.gmail.com>
Date: Fri, 28 Nov 2014 07:58:52 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Eduardo Valentin <edubezval@...il.com>
Cc: Linux PM <linux-pm@...r.kernel.org>,
Lukasz Majewski <l.majewski@...sung.com>,
LKML <linux-kernel@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Grant Likely <grant.likely@...aro.org>,
Kukjin Kim <kgene.kim@...sung.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
linux-samsung-soc <linux-samsung-soc@...r.kernel.org>,
Naveen Krishna Chatradhi <ch.naveen@...sung.com>,
Rob Herring <robh+dt@...nel.org>,
Zhang Rui <rui.zhang@...el.com>
Subject: Re: [PATCH 1/1] thermal: cpu_cooling: check for the readiness of
cpufreq layer
On 27 November 2014 at 19:38, Eduardo Valentin <edubezval@...il.com> wrote:
>> Acked-by: Viresh Kumar <viresh.kumar@...aro.org>
>
> 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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists