[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <39a142ae-e0a1-0683-d68c-128b388f480e@web.de>
Date: Tue, 15 Oct 2019 19:55:18 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Tomasz Figa <tomasz.figa@...il.com>, linux-clk@...r.kernel.org,
linux-samsung-soc@...r.kernel.org, kernel-janitors@...r.kernel.org
Cc: Chanwoo Choi <cw00.choi@...sung.com>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Sylwester Nawrocki <s.nawrocki@...sung.com>,
Aditya Pakki <pakki001@....edu>, Kangjie Lu <kjlu@....edu>,
Navid Emamdoost <emamd001@....edu>,
Stephen McCamant <smccaman@....edu>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: clk: samsung: Checking a kmemdup() call in
_samsung_clk_register_pll()
> That said, there is no need to print any warnings or error messages on
> allocation failure, so technically they could be removed.
Do you find information sufficient from the Linux allocation failure report?
Regards,
Markus
Powered by blists - more mailing lists