public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Rui Sousa <rui.p.m.sousa@gmail.com>, linux-next@vger.kernel.org
Subject: Re: linux-next: tip-core build failure
Date: Sun, 14 Sep 2008 20:36:29 +0200	[thread overview]
Message-ID: <20080914183629.GA28010@elte.hu> (raw)
In-Reply-To: <20080915040100.5a6f634f.sfr@canb.auug.org.au>


* Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi Ingo,
> 
> On Sun, 14 Sep 2008 14:43:20 +0200 Ingo Molnar <mingo@elte.hu> wrote:
> >
> > yes, i agree with that direction. But it's difficult: the non-x86 
> > architectures do not get much testing in practice at the development 
> > stage so trivial build bugs like this get only found at the latest 
> > stage. That's not actually bad in itself - stuff that is not used does 
> > not matter nearly as much as stuff that does get used.
> 
> Well, its not really that difficult, you just have to remember that x86
> is not the whole world [...]

[ ... just used by 90%+ of our active testers/developers ;-) ... ]

> [...] and touching generic code just might affect the other 
> architectures - especially when the code you are touching is using 
> stuff that is clearly implemented by the architectures. Posting stuff 
> like this to linux-arch usually gets some attention (my apologies if 
> you did so, I don't remember seeing it).

hm, you seem to have a bias for powerpc, but you should realize that 
cross-building for 20+ architectures (i.e. increasing the testing 
overhead twenty-fold), to cover the remaining <10% of the test space is 
unreasonable: for many developers it's not just virtually impossible in 
practice but also often a serious waste of time.

Most people who have ever tried to collect cross-compilers for _all_ 
architectures and managed to get them all to work, and then used them 
consistently for all their patches will agree with that.

We want to push unreasonable work to those who depend on the result of 
that unreasonable work - i.e. users/developers of those platforms - not 
everyone else. We dont want to hinder the progress of Linux with blindly 
requiring all patches that happen to touch common .c or .h files to 
successfully build on 20+ odd architectures.

... anyway, no real arguments about this specific case, if a fix/report 
is available we'll integrate/fix the issue.

	Ingo

  reply	other threads:[~2008-09-14 18:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-13  1:14 linux-next: tip-core build failure Stephen Rothwell
2008-09-13  9:44 ` Rui Sousa
2008-09-14 12:43   ` Ingo Molnar
2008-09-14 18:01     ` Stephen Rothwell
2008-09-14 18:36       ` Ingo Molnar [this message]
2008-09-14 19:02         ` Stephen Rothwell
2008-09-14 19:17           ` Ingo Molnar
2008-09-14 19:45             ` Stephen Rothwell
2008-09-15  8:11               ` Ingo Molnar
2008-09-15 13:02                 ` Rui Sousa

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=20080914183629.GA28010@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-next@vger.kernel.org \
    --cc=rui.p.m.sousa@gmail.com \
    --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