From: Ingo Molnar <mingo@elte.hu>
To: Patrick McHardy <kaber@trash.net>
Cc: David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org
Subject: Re: [bug] build failure in net/netfilter/nf_conntrack_sip.c, on latest -git
Date: Mon, 21 Apr 2008 21:31:47 +0200 [thread overview]
Message-ID: <20080421193147.GA8770@elte.hu> (raw)
In-Reply-To: <480C780C.2030402@trash.net>
* Patrick McHardy <kaber@trash.net> wrote:
>> for the last 3 days my own automated bug finding capacity is at 10%
>> of its normal throughput (it booted only 200 kernels, instead of 2000
>> kernels) - which is OK in early phases of the merge window, but you
>> seem to deny that i have any standing to argue development process
>> issues.
>
> In my perception networking is not doing worse than other subsystems,
> this (small) accumulation of build-bugs seems more like an unfortunate
> coincidence caused by two people being sloppy during testing (me and
> the LED guys).
nah, it's not doing worse at all and my comment was not really about the
bug itself (bugs happen), but about the most efficient way to report
that bug - which in hindsight is not an argument i should have gotten
into. arch/x86 has at least this proportion of build bugs if not more.
[and the scheduler is a 50 times smaller piece of code so it's not
really comparable.]
btw., managed to test 755 random kernels today:
#define UTS_VERSION "#755 SMP PREEMPT Mon Apr 21 21:12:52 CEST 2008"
with no runtime (or build) failure anywhere. [other than in freshly
added x86.git or scheduler patches that is.]
Ingo
next prev parent reply other threads:[~2008-04-21 19:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 10:00 [bug] build failure in net/netfilter/nf_conntrack_sip.c, on latest -git Ingo Molnar
2008-04-19 10:03 ` David Miller
2008-04-19 10:39 ` Ingo Molnar
2008-04-19 11:09 ` David Miller
2008-04-21 8:22 ` Ingo Molnar
2008-04-21 8:58 ` David Miller
2008-04-21 11:14 ` Ingo Molnar
2008-04-21 16:26 ` [bug] build failures, git trees Randy Dunlap
2008-04-21 21:42 ` David Miller
2008-04-21 11:18 ` [bug] build failure in net/netfilter/nf_conntrack_sip.c, on latest -git Patrick McHardy
2008-04-21 19:31 ` Ingo Molnar [this message]
2008-04-21 8:14 ` Jeff Garzik
2008-04-21 13:39 ` Ingo Molnar
2008-04-22 2:20 ` Herbert Xu
2008-04-19 10:07 ` David Miller
2008-04-19 10:41 ` Ingo Molnar
2008-04-19 11:10 ` David Miller
2008-04-19 10:44 ` Jan Engelhardt
2008-04-19 11:11 ` David Miller
2008-04-19 16:38 ` Patrick McHardy
2008-04-20 0:54 ` David Miller
2008-04-21 7:23 ` Jeff Garzik
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=20080421193147.GA8770@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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