10 Commits

Author	SHA1	Message	Date
Thomas Schoebel-Theuer	4d31d09534	all: remove CONFIG_MARS_BIGMODULE	2016-03-03 09:33:34 +01:00
Thomas Schoebel-Theuer	9cb5b54cdc	infra: remove outdated code	2015-03-23 13:48:11 +01:00
Thomas Schoebel-Theuer	aa09d7df30	all: clarify license GPLv2+	2014-11-25 18:09:17 +01:00
Thomas Schoebel-Theuer	d04562a39d	infra: adapt to new kthreads after 3.7	2014-06-18 12:10:55 +02:00
Thomas Schoebel-Theuer	7aebfdf6bb	all: remove __exit annotation	2014-04-24 18:08:31 +02:00
Thomas Schoebel-Theuer	08b27c548e	all: add lamport clock to all messages	2013-07-22 08:44:03 +02:00
Thomas Schoebel-Theuer	105bc07b58	infra: lamport clock can never appear as stopped ... In case CONFIG_HIGH_RES_TIMERS is not set (or when it does not work as expected), the lamport clock could "stop" in some extremely rare cases. Theoretically, a symlink update could be missed, or two transaction log records could accidentally get the same timestamp. We want any timestamps to be unique (at least on the same host). This patch ensures that true forward stepping always takes place, even when the system clock fails (or at other problems). For now, the dependency from CONFIG_HIGH_RES_TIMERS is left in Kconfig as a precondition for MARS. After some tests and some observational time, it could probably be removed some day.	2013-07-22 08:44:03 +02:00
Thomas Schoebel-Theuer	dfe2dc5b1c	infra: remove recursive button operations ... All buttons should be switched step-by-step in future. The previous patch should ensure that no harm can occur.	2013-06-03 09:05:46 +02:00
Thomas Schoebel-Theuer	db8e4caacf	proc: fix query of lamport clock	2013-05-13 12:50:29 +02:00
Thomas Schoebel-Theuer	c58417d271	all: move kernel source into separate directory	2013-04-08 17:01:37 +02:00