From: behanw@converseincode.com
To: agk@redhat.com, clm@fb.com, davem@davemloft.net,
dm-devel@redhat.com, fabf@skynet.be, herbert@gondor.apana.org.au,
jbacik@fb.com, snitzer@redhat.com
Cc: akpm@linux-foundation.org, james.l.morris@oracle.com,
john.johansen@canonical.com, linux-btrfs@vger.kernel.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-raid@vger.kernel.org,
linux-security-module@vger.kernel.org, neilb@suse.de,
serge@hallyn.com, torvalds@linux-foundation.org,
Behan Webster <behanw@converseincode.com>
Subject: [PATCH RFC 0/6] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM
Date: Tue, 2 Sep 2014 15:32:27 -0700 [thread overview]
Message-ID: <1409697153-7006-1-git-send-email-behanw@converseincode.com> (raw)
From: Behan Webster <behanw@converseincode.com>
These patches remove the use of Variable Length Arrays In Structs (VLAIS) in
crypto related code. Presented here for comments as a whole (since they all do
the same thing in the same way). Once everyone is happy I will submit them
individually to their appropriate maintainers.
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).
Jan-Simon Möller (4):
crypto, dm: LLVMLinux: Remove VLAIS usage from dm-crypt
crypto: LLVMLinux: Remove VLAIS usage from crypto/hmac.c
crypto: LLVMLinux: Remove VLAIS usage from libcrc32c.c
crypto: LLVMLinux: Remove VLAIS usage from crypto/testmgr.c
Vinícius Tinti (2):
apparmor: LLVMLinux: Remove VLAIS
btrfs: LLVMLinux: Remove VLAIS
crypto/hmac.c | 27 +++++++++++++--------------
crypto/testmgr.c | 16 ++++++++--------
drivers/md/dm-crypt.c | 38 ++++++++++++++++++--------------------
fs/btrfs/hash.c | 18 +++++++++---------
lib/libcrc32c.c | 18 +++++++++---------
security/apparmor/crypto.c | 19 +++++++++----------
6 files changed, 66 insertions(+), 70 deletions(-)
--
1.9.1
next reply other threads:[~2014-09-02 22:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 22:32 behanw [this message]
2014-09-02 22:32 ` [PATCH RFC 1/6] crypto, dm: LLVMLinux: Remove VLAIS usage from dm-crypt behanw
2014-09-02 22:32 ` [PATCH RFC 2/6] crypto: LLVMLinux: Remove VLAIS usage from crypto/hmac.c behanw
2014-09-02 22:32 ` [PATCH RFC 3/6] crypto: LLVMLinux: Remove VLAIS usage from libcrc32c.c behanw
2014-09-02 22:32 ` [PATCH RFC 4/6] crypto: LLVMLinux: Remove VLAIS usage from crypto/testmgr.c behanw
2014-09-02 22:32 ` [PATCH RFC 5/6] apparmor: LLVMLinux: Remove VLAIS behanw
2014-09-02 23:16 ` John Johansen
2014-09-02 23:26 ` Behan Webster
2014-09-02 22:32 ` [PATCH RFC 6/6] btrfs: " behanw
2014-09-02 23:01 ` [PATCH RFC 0/6] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM Marcel Holtmann
2014-09-02 23:04 ` Jan-Simon Möller
2014-09-02 23:07 ` Behan Webster
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=1409697153-7006-1-git-send-email-behanw@converseincode.com \
--to=behanw@converseincode.com \
--cc=agk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=clm@fb.com \
--cc=davem@davemloft.net \
--cc=dm-devel@redhat.com \
--cc=fabf@skynet.be \
--cc=herbert@gondor.apana.org.au \
--cc=james.l.morris@oracle.com \
--cc=jbacik@fb.com \
--cc=john.johansen@canonical.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=neilb@suse.de \
--cc=serge@hallyn.com \
--cc=snitzer@redhat.com \
--cc=torvalds@linux-foundation.org \
/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).