All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Li <sparse@chrisli.org>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: Warning message when using sparse
Date: Fri, 9 Jul 2010 15:04:20 -0700	[thread overview]
Message-ID: <AANLkTikFmeXz9og4t98jm6QcAdRa6rIeCAv3oeFnTgd8@mail.gmail.com> (raw)
In-Reply-To: <4C3793FB.4080907@gmail.com>

On Fri, Jul 9, 2010 at 2:26 PM, Jiri Slaby <jirislaby@gmail.com> wrote:
> On 07/09/2010 11:22 PM, Larry Finger wrote:
>> Obviously, I pulled the wrong git tree. I got the one from the wiki.
>> When I built the one from the kernel.org tree, all is well.
>
> Both are from kernel.org. But the one I sent is a Chris'es "fork" with
> my and other fixes.
>

Yes, you caught me slacking off. It is time to cut a new release
and flush all the bits into the official tree.

Chris

  reply	other threads:[~2010-07-09 22:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-09  1:52 Warning message when using sparse Larry Finger
2010-07-09 20:47 ` Jiri Slaby
2010-07-09 21:22   ` Larry Finger
2010-07-09 21:26     ` Jiri Slaby
2010-07-09 22:04       ` Christopher Li [this message]
2010-07-10  8:39         ` [PATCH 1/2] parser: fix and simplify support of asm goto Jiri Slaby
2010-07-10 18:36           ` Chris Li
2010-07-10 18:36             ` Chris Li
2010-07-10  8:39         ` [PATCH 2/2] parser: define __builtin_unreachable Jiri Slaby
2010-07-10  9:07           ` Josh Triplett
2010-07-13  7:52             ` Chris Li
2010-07-13  7:52               ` Chris Li
2010-07-13 18:12               ` Josh Triplett
2010-07-13 18:49                 ` Chris Li
2010-07-13 18:49                   ` Chris 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=AANLkTikFmeXz9og4t98jm6QcAdRa6rIeCAv3oeFnTgd8@mail.gmail.com \
    --to=sparse@chrisli.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.