Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752968AbdGSJGv (ORCPT ); Wed, 19 Jul 2017 05:06:51 -0400 Received: from mail-ua0-f176.google.com ([209.85.217.176]:35779 "EHLO mail-ua0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752026AbdGSJGt (ORCPT ); Wed, 19 Jul 2017 05:06:49 -0400 MIME-Version: 1.0 In-Reply-To: References: <20170718101730.2541-1-jonas.gorski@gmail.com> <20170718101730.2541-5-jonas.gorski@gmail.com> From: Jonas Gorski Date: Wed, 19 Jul 2017 11:06:28 +0200 Message-ID: Subject: Re: [PATCH 4/9] m68k: allow NULL clock for clk_get_rate To: Greg Ungerer Cc: Geert Uytterhoeven , linux-m68k@vger.kernel.org, "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 846 Lines: 27 Hi Greg, On 18 July 2017 at 14:03, Greg Ungerer wrote: > Hi Jonas, > > On 18/07/17 20:17, Jonas Gorski wrote: >> >> Make the behaviour of clk_get_rate consistent with common clk's >> clk_get_rate by accepting NULL clocks as parameter. Some device >> drivers rely on this, and will cause an OOPS otherwise. >> >> Fixes: facdf0ed4f59 ("m68knommu: introduce basic clk infrastructure") >> Cc: Greg Ungerer > > > Acked-by: Greg Ungerer > > Do you want me to push this via the m68knommu git tree? > Or are you (or someone) taking the series as a whole? Please take it through your tree. I totally forgot mentioning in the cover letter that I'm just a simple patch submitter and don't have my own tree. Too long ago that I sent a multi-tree patch series last time ... . Regards Jonas