Re: [PATCH v3 2/4] tracing: Make syscall_(un)regfunc arch-specific

[Peter Zijlstra]

On Mon, 2009-08-24 at 13:52 +0200, Ingo Molnar wrote:
> * Paul Mundt <lethal@xxxxxxxxxxxx> wrote:
> 
> > On Mon, Aug 24, 2009 at 11:56:52AM +0200, Ingo Molnar wrote:
> 
> > > So i'd really like you to back up your claims with facts. Your 
> > > mail is basically unsubstantiated FUD right now and i'll just 
> > > ignore you if you continue this pattern of unsubstantiated 
> > > attacks and unconstructive behavior.
> > 
> > I could sit here and itemize individual breakages all day long, 
> > but what would be the point? [...]
> 
> The point would be to prove your so far unsubstantiated (and IMO 
> unfair) attacks.

Guys, can we get over this already.. really every linux developer runs
x86, except the very few that don't. We all try to ensure we don't
accidentally break things, shit happens, deal with it.

!x86 breaking more often than x86 is a simple consequence of statistics,
if you don't like it, make your hardware sexy and send it to more
devs ;-)

Build breakages aren't a big deal, they get sorted, life moves on. If
they wouldn't get sorted there might be something to complain about, but
afaict that doesn't happen.

Paul, you put a tracing patch into the sh tree, didn't cc the tracing
folks and then found it broke when the tracing tree was added, *gosh*!?

That will happen with pretty much every other subsystem too, that's what
we have subsystem tree's for, I think enough has been arranged to
mitigate this issue in the future - lets go fix some real bugs now? :-)


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/