From: Christopher Li <sparse@chrisli.org>
To: Kamil Dudka <kdudka@redhat.com>
Cc: Jeff Garzik <jeff@garzik.org>,
Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH] compile-i386: do not generate an infinite loop
Date: Wed, 22 Jul 2009 12:30:42 -0700 [thread overview]
Message-ID: <70318cbf0907221230o3f96ace7yc8e1d409e75891b2@mail.gmail.com> (raw)
In-Reply-To: <200907221921.58947.kdudka@redhat.com>
On Wed, Jul 22, 2009 at 10:21 AM, Kamil Dudka<kdudka@redhat.com> wrote:
> Sorry for my ignorance, I've never heard about the Linus filter. Could you
> please point me to some relevant info? For now we only want to play with
> separation logic and use it for static analysis of code as part of our
> research at FIT BUT.
Of course you haven't heard of it. I just make it up myself. A Linus filter
is a program that take bad C code as input and output good C code as if
it is written by Linus himself. We just need to hook it to LKML.
Chris
next prev parent reply other threads:[~2009-07-22 19:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 21:34 [PATCH] compile-i386: do not generate an infinite loop Kamil Dudka
2009-07-22 8:38 ` Christopher Li
2009-07-22 9:24 ` Kamil Dudka
2009-07-22 16:34 ` Christopher Li
2009-07-22 17:21 ` Kamil Dudka
2009-07-22 19:30 ` Christopher Li [this message]
2009-07-22 12:45 ` Jeff Garzik
2009-07-22 16:39 ` Christopher Li
2009-07-22 16:51 ` Jeff Garzik
2009-07-22 17:02 ` Kamil Dudka
2009-07-22 19:18 ` 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=70318cbf0907221230o3f96ace7yc8e1d409e75891b2@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=jeff@garzik.org \
--cc=kdudka@redhat.com \
--cc=linux-sparse@vger.kernel.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).