[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <7933ce8f-ca1b-6ed8-14b9-59679130dc47@web.de>
Date: Sat, 12 Oct 2019 16:17:03 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: linux-clk@...r.kernel.org, linux-samsung-soc@...r.kernel.org,
Chanwoo Choi <cw00.choi@...sung.com>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Sylwester Nawrocki <s.nawrocki@...sung.com>,
Tomasz Figa <tomasz.figa@...il.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org, Aditya Pakki <pakki001@....edu>,
Kangjie Lu <kjlu@....edu>, Navid Emamdoost <emamd001@....edu>,
Stephen McCamant <smccaman@....edu>
Subject: clk: samsung: Checking a kmemdup() call in
_samsung_clk_register_pll()
Hello,
I tried another script for the semantic patch language out.
This source code analysis approach points out that the implementation
of the function “_samsung_clk_register_pll” contains also a call
of the function “kmemdup”.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/clk/samsung/clk-pll.c?id=1c0cc5f1ae5ee5a6913704c0d75a6e99604ee30a#n1275
https://elixir.bootlin.com/linux/v5.4-rc2/source/drivers/clk/samsung/clk-pll.c#L1275
* Do you find the usage of the format string “%s: could not allocate
rate table for %s\n” still appropriate at this place?
* Is there a need to adjust the error handling here?
Regards,
Markus
Powered by blists - more mailing lists