[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <43617d6a-c778-629b-81b0-aa0accf09d80@web.de>
Date: Wed, 16 Oct 2019 13:58:04 +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()
> A backtrace should be enough for this kind of a failure that shouldn't
> normally happen and if happens, then the rest of the system must be in
> a state already about to fail anyway.
Does this feedback mean that you would like to omit two extra
error messages from this function implementation?
Regards,
Markus
Powered by blists - more mailing lists