From: John Cherry <cherry@osdl.org>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 2 New compile/sparse warnings (nightly build)
Date: Fri, 27 Aug 2004 09:17:51 -0700 [thread overview]
Message-ID: <1093623471.2467.50.camel@cherrybomb.pdx.osdl.net> (raw)
In-Reply-To: <20040827152551.GI21964@parcelfarce.linux.theplanet.co.uk>
On Fri, 2004-08-27 at 08:25, viro@parcelfarce.linux.theplanet.co.uk
wrote:
> On Fri, Aug 27, 2004 at 08:09:10AM -0700, John Cherry wrote:
> > Summary:
> > New warnings = 2
> > Fixed warnings = 8
>
> Hmm... What .config are you using? There was a bunch of sound/oss
> check_region() removals, etc.
Al, this summary is just a for a daily build (24-hour period). I only
post this when new warnings appear. There have been a bunch of fixed
warning over the past several weeks that have not been posted.
>
> Here I'm running builds on allmodconfig and allomodconfig with added
> 'SMP depends on BROKEN' to catch the BROKEN_ON_SMP drivers.
prev parent reply other threads:[~2004-08-27 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 15:09 John Cherry
2004-08-27 15:25 ` viro
2004-08-27 16:14 ` John Cherry
2004-08-27 16:17 ` 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=1093623471.2467.50.camel@cherrybomb.pdx.osdl.net \
--to=cherry@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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®