linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: Christopher Li <sparse@chrisli.org>,
	linux-sparse@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: RFC: Move sparse.git inside linux-kernel-2.6.git?
Date: Thu, 18 Jun 2009 22:18:40 +0200	[thread overview]
Message-ID: <20090618201840.GA14661@uranus.ravnborg.org> (raw)
In-Reply-To: <4A3A96E2.5080504@garzik.org>

> 
> Even though I _am_ one of those weirdos that would love to 
> sparse+something become the official kernel compiler -- many years from 
> now -- I think that they are best kept separate.
> 
> sparse -does- serve as "libsparse" to a few independent projects, and 
> the current sparse/kernel has clear benefits for those projects.  Being 
> a separate project helps keep sparse small, simple, focused and 
> portable, IMO.

"housing" the source inside the kernel source tree should not
be an excuse to make this kernel only.
It should rather expose the source.

And then people could extend sparse and say that they contributes
to the linux kernel. Maybe that could make it more sexy.

I at least does not see that housing the source inside the kernel
automatically will make it kernel only.
But I on the other hand are sure we will see additional
contributions / improvements and extended use.

Having sparse inside the kernel is therefore in no way a blocker
for smatch, or Jeff's x86 compilter toy.

	Sam

  parent reply	other threads:[~2009-06-18 20:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18 19:20 RFC: Move sparse.git inside linux-kernel-2.6.git? Sam Ravnborg
2009-06-18 19:34 ` Jeff Garzik
2009-06-18 19:57   ` Jeff Garzik
2009-06-18 20:13     ` Randy Dunlap
2009-06-18 20:18   ` Sam Ravnborg [this message]
2009-06-18 20:40 ` Christopher Li
2009-06-20 19:37   ` Samuel Bronson
2009-06-21 18:33     ` Christopher Li
2009-06-21 23:17       ` Samuel Bronson
2009-06-22  7:57         ` Christopher Li
2009-06-25 14:48         ` H. Peter Anvin
2009-07-02 23:21 ` Josh Triplett
2009-07-02 23:46   ` Christopher Li

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=20090618201840.GA14661@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=jeff@garzik.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=sparse@chrisli.org \
    --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).