linux-kernel - Re: [tip:timers/core] timekeeping: Increase granularity of read_persistent

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <19091.46451.893720.573893@cargo.ozlabs.ibm.com>
Date:	Tue, 25 Aug 2009 19:57:07 +1000
From:	Paul Mackerras <paulus@...ba.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Martin Schwidefsky <schwidefsky@...ibm.com>, dwalker@...o99.com,
	mingo@...hat.com, hpa@...or.com, linux-kernel@...r.kernel.org,
	johnstul@...ibm.com, tglx@...utronix.de,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:timers/core] timekeeping: Increase granularity of
	read_persistent_clock()

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. :)

I do think that it's reasonable to expect that a patch which touches
the architecture-specific code for some architecture gets compiled
for that architecture at least once before it gets set in stone.  As
far as I can tell, this didn't happen in the case of Martin's patch
that triggered this debate.

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 (http://kisskb.ellerman.id.au/) to build a
selection of configs and architectures automatically.

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