I grant you that this would be an interesting research project, but Linus isn't going to rip out the internals of the linux kernel, start from scratch, and re-implement everything in Lisp just for kicks. Too much work for too little return, and Iron Lisp is still not as performant as C. Also(I would confidently wager) more kernel programmers are proficient in C than in Lisp, at least for systems programming.
It's difficult to take the question seriously rather than as an attention-grab.
Not to mention that one of the main arguments for using Lisp was "Lisp programs are less buggy than C programs". That's assuming that you trust your Lisp implementation. All implementing it in Common Lisp does is move some of the potential bugs from the kernel to the Lisp implementation.
Comments
I grant you that this would be an interesting research project, but Linus isn't going to rip out the internals of the linux kernel, start from scratch, and re-implement everything in Lisp just for kicks. Too much work for too little return, and Iron Lisp is still not as performant as C. Also(I would confidently wager) more kernel programmers are proficient in C than in Lisp, at least for systems programming.
It's difficult to take the question seriously rather than as an attention-grab.
Not to mention that one of the main arguments for using Lisp was "Lisp programs are less buggy than C programs". That's assuming that you trust your Lisp implementation. All implementing it in Common Lisp does is move some of the potential bugs from the kernel to the Lisp implementation.