From: Behan Webster <behanw@converseincode.com>
To: plagnioj@jcrosoft.com, tomi.valkeinen@ti.com
Cc: behanw@converseincode.com, archit@ti.com, daniel.vetter@ffwll.ch,
geert@linux-m68k.org, laurent.pinchart@ideasonboard.com,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, robdclark@gmail.com
Subject: [PATCH 0/2] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM
Date: Sat, 27 Sep 2014 01:10:51 +0000 [thread overview]
Message-ID: <1411780253-4492-1-git-send-email-behanw@converseincode.com> (raw)
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(-)
--
1.9.1
next reply other threads:[~2014-09-27 1:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-27 1:10 Behan Webster [this message]
2014-09-27 1:10 ` [PATCH 1/2] arm, fbdev, omap2, LLVMLinux: Remove nested function from omap2 dss Behan Webster
2014-09-27 16:46 ` Felipe Balbi
2014-09-27 22:53 ` Behan Webster
2014-09-27 1:10 ` [PATCH 2/2] arm, fbdev, omap2, LLVMLinux: Remove nested function from omapfb Behan Webster
2014-09-27 16:46 ` Felipe Balbi
2014-09-30 10:15 ` [PATCH 0/2] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM Tomi Valkeinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1411780253-4492-1-git-send-email-behanw@converseincode.com \
--to=behanw@converseincode.com \
--cc=archit@ti.com \
--cc=daniel.vetter@ffwll.ch \
--cc=geert@linux-m68k.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--cc=robdclark@gmail.com \
--cc=tomi.valkeinen@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).