| 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
| ||
|
Message-Id: <1451297429-21689-1-git-send-email-yamada.masahiro@socionext.com> Date: Mon, 28 Dec 2015 19:10:13 +0900 From: Masahiro Yamada <yamada.masahiro@...ionext.com> To: linux-mtd@...ts.infradead.org Cc: Masahiro Yamada <yamada.masahiro@...ionext.com>, Stephen Boyd <sboyd@...eaurora.org>, Michael Turquette <mturquette@...libre.com>, linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org Subject: [PATCH v2 00/16] clk: a collection of various clean-ups and improvements Many refactoring, with detection of circular parent looping. Changes in v2: - Fix a bug. Return -EINVAL when parent _is_ NULL. Masahiro Yamada (16): clk: remove unused first argument of __clk_init() clk: change the argument of __clk_init() into pointer to clk_core clk: rename __clk_init() into __clk_core_init() clk: remove unnecessary !core->parents conditional clk: change sizeof(struct clk *) to sizeof(*core->parents) clk: move core->parents allocation to clk_register() clk: simplify clk_core_get_parent_by_index() clk: drop the initial core->parents look-ups from __clk_core_init() clk: replace pr_warn() with pr_err() for fatal cases clk: move checking .git_parent to __clk_core_init() clk: simplify __clk_init_parent() clk: avoid circular clock topology clk: walk the orphan clock list more simply clk: make sure parent is not NULL in clk_fetch_parent_index() clk: simplify clk_fetch_parent_index() function clk: slightly optimize clk_core_set_parent() drivers/clk/clk.c | 214 ++++++++++++++++++++++-------------------------------- 1 file changed, 85 insertions(+), 129 deletions(-) -- 1.9.1 -- 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