From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: -next build logs
Date: Wed, 27 Feb 2008 00:36:13 +0100 [thread overview]
Message-ID: <47C4A26D.1030109@s5r6.in-berlin.de> (raw)
In-Reply-To: <20080227101338.5089d72d.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> On Tue, 26 Feb 2008 19:15:37 +0100 Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
>> the allmodconfig builds at http://kisskb.ellerman.id.au/kisskb/branch/9/
>> seem to lack a few drivers even though they are properly enabled in the
>> respective config. Is it simply because everything is rebuilt on top of
>> a previous build?
>
> That's interesting. I thought they were built from a clean tree each
> time but I will discuss this with Michael Ellerman who created this build
> system.
I noticed it while looking how well drivers/firewire/ (CONFIG_FIREWIRE*)
and drivers/ieee1394/ (CONFIG_IEEE1394*) are compiled in -next; i.e. you
can just check for the firewire ones as one example of potentially
missing compiles. On the other hand, I also saw some LDs without
corresponding preceding CCs, so it rather looks like there was already
something compiled.
>> Do you mail only errors to maintainers or also compiler warnings?
>
> Currently I am only concerned with actual failures.
OK, I will just look myself into the logs then. Thanks,
--
Stefan Richter
-=====-==--- --=- ==-==
http://arcgraph.de/sr/
next prev parent reply other threads:[~2008-02-26 23:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 18:15 Stefan Richter
2008-02-26 23:13 ` Stephen Rothwell
2008-02-26 23:36 ` Stefan Richter [this message]
2008-02-27 6:06 ` Stephen Rothwell
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=47C4A26D.1030109@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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®