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-next>] [day] [month] [year] [list]
Message-Id: <1423251765-2947-1-git-send-email-sboyd@codeaurora.org>
Date:	Fri,  6 Feb 2015 11:42:42 -0800
From:	Stephen Boyd <sboyd@...eaurora.org>
To:	Mike Turquette <mturquette@...aro.org>,
	Stephen Boyd <sboyd@...eaurora.org>
Cc:	linux-kernel@...r.kernel.org,
	Sylwester Nawrocki <s.nawrocki@...sung.com>,
	Alban Browaeys <alban.browaeys@...il.com>,
	Tomeu Vizoso <tomeu.vizoso@...labora.com>
Subject: [PATCH v2 0/3] CCF fixes/cleanup for per-user series

Here are some fixes from yesterdays's dive into the fallout from the
per-user constraints patches. We should do a final sweep later
to rename local variables with type struct clk_core to core.

Changes from v1:
 * Picked up tags
 * Dropped clk.h include in last patch
 * Handled IS_ERR() retrurn from __clk_create_clk() in clkdev in first patch
 * Removed dead comment in last patch

Stephen Boyd (3):
  clkdev: Always allocate a struct clk and call __clk_get() w/ CCF
  clk: Rename child_node to clks_node to avoid confusion
  clk: Replace of_clk_get_by_clkspec() with of_clk_get_from_provider()

 drivers/clk/clk-conf.c |  7 +++---
 drivers/clk/clk.c      | 60 +++++++++++++++++++++++++++-----------------------
 drivers/clk/clk.h      | 22 ++++++++++++++----
 drivers/clk/clkdev.c   | 57 ++++++++++-------------------------------------
 4 files changed, 66 insertions(+), 80 deletions(-)

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ