All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Ryan Anderson <ryan@michonline.com>,
	linux-kernel@vger.kernel.org, postmaster@vger.kernel.org
Subject: Re: sparse errors
Date: Wed, 28 May 2003 16:35:13 +0200	[thread overview]
Message-ID: <3ED4C921.5080902@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0305280703520.7569-100000@home.transmeta.com>

Linus Torvalds wrote:
> On Wed, 28 May 2003, Ryan Anderson wrote:
> 
>>I'm not totally grokking how sparse is put together yet, but I've got
>>this:
[...]
>>Should this be cc:ed to linux-kernel, or do you have another place in
>>mind?
> 
> 
> It probably shouldn't be CC'd to linux-kernel, but there isn't any other 
> place either.
> 
> 		Linus

Maybe create a new list:

linux-source-analyzers@vger.kernel.org

or something like that.


Carl-Daniel


  reply	other threads:[~2003-05-28 14:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28  5:38 sparse errors Ryan Anderson
2003-05-28 14:16 ` Linus Torvalds
2003-05-28 14:35   ` Carl-Daniel Hailfinger [this message]
2003-05-28 14:51     ` Dave Jones
2003-05-28 14:39 ` Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2019-03-28 18:34 Sparse errors Bharath Vedartham
2019-03-28 18:37 ` Greg KH
2019-03-28 19:03   ` Ozgur Kara
2019-03-28 19:23   ` Bharath Vedartham
2019-03-28 18:57 ` Ozgur Kara
2019-03-28 19:24   ` Bharath Vedartham
2021-05-25 19:32 Pierre-Louis Bossart
2021-05-26  6:02 ` Dan Carpenter
2021-05-26  7:40 ` Takashi Iwai
2021-05-26 14:17   ` Pierre-Louis Bossart
2021-05-26 15:21     ` Takashi Iwai
2021-05-26 15:24     ` Dan Carpenter

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=3ED4C921.5080902@gmx.net \
    --to=c-d.hailfinger.kernel.2003@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=postmaster@vger.kernel.org \
    --cc=ryan@michonline.com \
    --cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.