From: John Cherry <cherry@osdl.org>
To: Dave Jones <davej@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 10 New compile/sparse warnings (overnight build)
Date: Thu, 09 Sep 2004 11:22:13 -0700 [thread overview]
Message-ID: <1094754133.6867.51.camel@cherrypit.pdx.osdl.net> (raw)
In-Reply-To: <20040909172921.GB19843@redhat.com>
The sparse binary is being updated every two weeks. I am trying to
avoid mining reasonable data with a changing kernel AND a changing
sparse tool.
John
On Thu, 2004-09-09 at 10:29, Dave Jones wrote:
> On Thu, Sep 09, 2004 at 09:39:27AM -0700, John Cherry wrote:
> > Sorry about the duplicate entries. I'll fix the tool. There are really
> > just 7 new sparse warnings.
>
> Out of curiosity, how often is the sparse binary being updated
> in this automated check ?
>
> Dave
prev parent reply other threads:[~2004-09-09 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 14:57 John Cherry
2004-09-09 16:39 ` John Cherry
2004-09-09 17:29 ` Dave Jones
2004-09-09 18:22 ` John Cherry [this message]
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=1094754133.6867.51.camel@cherrypit.pdx.osdl.net \
--to=cherry@osdl.org \
--cc=davej@redhat.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®