Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755870AbbBLN67 (ORCPT ); Thu, 12 Feb 2015 08:58:59 -0500 Received: from bhuna.collabora.co.uk ([93.93.135.160]:48814 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755282AbbBLN6y (ORCPT ); Thu, 12 Feb 2015 08:58:54 -0500 From: Javier Martinez Canillas To: Mike Turquette Cc: Stephen Boyd , Tomeu Vizoso , =?UTF-8?q?Emilio=20L=C3=B3pez?= , Peter De Schrijver , Robert Jarzmik , Giuseppe Cavallaro , linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org, Javier Martinez Canillas Subject: [PATCH v2 0/3] clk: Some fixes for the per-user clk API changes. Date: Thu, 12 Feb 2015 14:58:27 +0100 Message-Id: <1423749510-14525-1-git-send-email-javier.martinez@collabora.co.uk> X-Mailer: git-send-email 2.1.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1299 Lines: 35 Hello, This is a v2 of a series to fix some issues found on linux-next after the per-user clk API changes were introduced. Booting an Exynos5420 Peach Pit Chromebook and using a composite clock makes the system to crash due a NULL pointer dereference error. A previous version of the series is [0] and this addresses issues pointed out by Stephen Boyd. This series is composed of the following patches: Javier Martinez Canillas (3): clk: Don't dereference parent clock if is NULL clk: Add __clk_hw_set_clk helper function clk: Replace explicit clk assignment with __clk_hw_set_clk drivers/clk/clk-composite.c | 20 ++++++++++---------- drivers/clk/clk.c | 4 ++-- drivers/clk/pxa/clk-pxa.c | 2 +- drivers/clk/st/clk-flexgen.c | 20 ++++++++++---------- drivers/clk/st/clkgen-mux.c | 14 +++++++------- drivers/clk/tegra/clk-periph.c | 14 +++++++------- include/linux/clk-provider.h | 6 ++++++ 7 files changed, 43 insertions(+), 37 deletions(-) Best regards, Javier [0]: https://lkml.org/lkml/2015/2/11/139 -- 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/