Re: [tip:timers/core] timekeeping: Increase granularity ofread_persistent_clock()

From: Paul Mackerras
Date: Tue Aug 25 2009 - 07:33:25 EST

Ingo Molnar writes:

> * Paul Mackerras <paulus@xxxxxxxxx> wrote:
> > Ingo Molnar writes:
> >
> > > If you suggest that each and every subsystem maintainer who
> > > touches code that can be built on non-x86 architectures has to
> > > cross-build to 20+ architectures to be able to push out a tree,
> > > all the time, and has to rebase if this ever gets omitted, you
> > > are really defying reality and are hurting Linux.
> >
> > Nice straw man, but I never said or even suggested anything like
> > that. :)
> ... but what you say in essence amounts to that. Every change to a
> file that is built on an architecture 'affects' that architecture so
> your arguments can be repeated for that one. It's a slippery slope
> built on a wrong premise.

Not at all. I'm saying that committing code, some of which has never
ever been compiled on any architecture, is just sloppy. It's basic
good engineering practice to have at least compiled the code you're
committing - at least once on at least one architecture. It's like
making changes inside #ifdef CONFIG_FOO but never testing with
CONFIG_FOO turned on. You'd complain, and rightly, if someone did

> I can only repeat what i said because i did not see you really
> counter the core of my argument (you snipped out much of my mail
> that details this and only replied to the last paragraph):

Well, though much of what you said is true, in the end it seems to
boil down to saying that non-x86 architectures don't have any right to
expect any degree of care or attention from you, because only x86 is
important. And of course you have a perfect right to pay attention to
whatever you find interesting and ignore anything else, including
difficulties that you cause along the way for other kernel developers.

There doesn't seem to be any useful response to that.

> Say that patch also touches arch/xtensa/. Can you cross-build to
> xtensa?

Sure, I just ask Michael Ellerman to point kisskb at a tree with my
proposed patch in it.

> > Patches which touch multiple architecture's arch-specific code
> > should also get sent to the maintainers of the affected
> > architectures and the linux-arch mailing list. I don't recall
> > seeing this patch on linux-arch, though I may have missed it (and
> > anyway that would be Martin's responsibility not yours, but it
> > does contribute to the sense of being blindsided).
> >
> > More generally - if you don't have the resources to do regular
> > build testing for powerpc or other architectures, then publish a
> > testing branch and we'll get kisskb
> > ( to build a selection of configs
> > and architectures automatically.
> Slowing down patches via buerocracy like that is not acceptable at
> all. Make developers care more about your architecture via natural
> means, not via buerocratic measures.

The "should" in what I said is just good manners, not bureaucracy.

The stuff about kisskb was an offer to help, not bureaucracy.
No-one's forcing you to do anything.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at