[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4a7d20c9-d080-80a4-6529-bc9fa1b7a186@users.sourceforge.net>
Date: Fri, 16 Sep 2016 07:32:33 +0200
From: SF Markus Elfring <elfring@...rs.sourceforge.net>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: linux-clk <linux-clk@...r.kernel.org>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Michael Turquette <mturquette@...libre.com>,
Simon Horman <horms+renesas@...ge.net.au>,
Stephen Boyd <sboyd@...eaurora.org>,
Ulf Hansson <ulf.hansson@...aro.org>,
LKML <linux-kernel@...r.kernel.org>,
"kernel-janitors@...r.kernel.org" <kernel-janitors@...r.kernel.org>,
Julia Lawall <julia.lawall@...6.fr>
Subject: Re: clk/Renesas-MSTP: Less function calls in cpg_mstp_clocks_init()
after error detection
>> * Should it usually be determined quicker if a required resource like
>> memory could be acquired before trying the next allocation?
>
> Note that if memory allocation fails in this driver, the system won't
> boot at all.
Thanks for this information.
> So even not checking for allocation failures at all could be acceptable.
I find this opinion interesting somehow.
I would generally prefer to check return values from various function calls
immediately instead of keeping the discussed source code structure unchanged.
Regards,
Markus
Powered by blists - more mailing lists