Hi, On Tue, 18 Feb 2014 12:46:13 -0800 Behan Webster <behanw@xxxxxxxxxxxxxxxxxx> wrote: > > I'm assuming this is the right way to ask about being added to > linux-next. If it isn't please point me in the right direction. Correct, but usually you would cc any interested parties so that I can get some feel for when this code might be merged into Linus' tree. > The LLVMLinux project would like to participate in the linux-next tree > if possible. We have a branch in our kernel git tree now into which we > have put some of our patches. At the moment, the patches in next are > some of the most core changes which enable clang in Kbuild, but don't > get in the way of the use of gcc.We'll put more patches in the branch as > our other changes are accepted. We'd like more visibility of some of the > changes we'd like in order to enable clang, and a way to help make sure > that we aren't breaking anything in other people's work. > > http://git.linuxfoundation.org/llvmlinux/kernel.git (for-next branch) Normally you would cite the git:// URL .. > Otherwise we're publishing all of our patches in the master branch of > this git tree. Currently we're working on enabling clang support for > x86, arm, and arm64. > > The LLVMLinux project is working on changes to the LLVM/clang toolchain > as well as to the linux kernel code in order to be able to compile the > kernel with clang. I have no objection to this, but would like to see more of these patches reviewed by (among others) the kbuild guys (cc'd). I also could not find some of these patches published on lkml (where I would expect to see them). And the top patch has a very uninformative commit message :-( -- Cheers, Stephen Rothwell sfr@xxxxxxxxxxxxxxxx
Attachment:
pgpTRTzZkvLhR.pgp
Description: PGP signature
