[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <542A82C6.7090607@ti.com>
Date: Tue, 30 Sep 2014 13:15:34 +0300
From: Tomi Valkeinen <tomi.valkeinen@...com>
To: Behan Webster <behanw@...verseincode.com>, <plagnioj@...osoft.com>
CC: <daniel.vetter@...ll.ch>, <geert@...ux-m68k.org>,
<laurent.pinchart@...asonboard.com>, <linux-fbdev@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-omap@...r.kernel.org>,
<robdclark@...il.com>
Subject: Re: [PATCH 0/2] LLVMLinux: Patches to enable the kernel to be compiled
with clang/LLVM
On 27/09/14 04:10, Behan Webster wrote:
> Replace the use of nested functions where a normal function will suffice.
>
> Nested functions are not liked by upstream kernel developers in general. Their
> use breaks the use of clang as a compiler, and doesn't make the code any
> better.
>
> This code now works for both gcc and clang.
>
> The LLVMLinux project aims to fully build the Linux kernel using both gcc and
> clang (the C front end for the LLVM compiler infrastructure project).
>
> Behan Webster (2):
> arm, fbdev, omap2, LLVMLinux: Remove nested function from omap2 dss
> arm, fbdev, omap2, LLVMLinux: Remove nested function from omapfb
>
> drivers/video/fbdev/omap2/dss/dispc-compat.c | 9 +++++----
> drivers/video/fbdev/omap2/dss/manager-sysfs.c | 16 +++++++++-------
> drivers/video/fbdev/omap2/omapfb/omapfb-main.c | 14 +++++++-------
> 3 files changed, 21 insertions(+), 18 deletions(-)
>
I have to say I do like small helper funcs as nested functions, as they
are restricted inside the parent function's scope. But, of course,
nested funcs have their issues.
So looks fine to me, queuing for 3.18.
Tomi
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists