)]}' { "log": [ { "commit": "80a05b9ffa7dc13f6693902dd8999a2b61a3a0d7", "tree": "5612eeb26804b135de66779d1a00eaf35a4ceca1", "parents": [ "ad6759fbf35d104dbf573cd6f4c6784ad6823f7e" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Fri Mar 12 17:34:14 2010 +0100" }, "committer": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Fri Mar 12 19:10:29 2010 +0100" }, "message": "clockevents: Sanitize min_delta_ns adjustment and prevent overflows\n\nThe current logic which handles clock events programming failures can\nincrease min_delta_ns unlimited and even can cause overflows.\n\nSanitize it by:\n - prevent zero increase when min_delta_ns \u003d\u003d 1\n - limiting min_delta_ns to a jiffie\n - bail out if the jiffie limit is hit\n - add retries stats for /proc/timer_list so we can gather data\n\nReported-by: Uwe Kleine-Koenig \u003cu.kleine-koenig@pengutronix.de\u003e\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n" }, { "commit": "97813f2fe77804a4464564c75ba8d8826377feea", "tree": "5dc7154c5687edaee5712408c8baf605463ff093", "parents": [ "27185016b806d5a1181ff501cae120582b2b27dd" ], "author": { "name": "Jon Hunter", "email": "jon-hunter@ti.com", "time": "Tue Aug 18 12:45:11 2009 -0500" }, "committer": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Fri Nov 13 20:46:24 2009 +0100" }, "message": "nohz: Allow 32-bit machines to sleep for more than 2.15 seconds\n\nIn the dynamic tick code, \"max_delta_ns\" (member of the\n\"clock_event_device\" structure) represents the maximum sleep time\nthat can occur between timer events in nanoseconds.\n\nThe variable, \"max_delta_ns\", is defined as an unsigned long\nwhich is a 32-bit integer for 32-bit machines and a 64-bit\ninteger for 64-bit machines (if -m64 option is used for gcc).\nThe value of max_delta_ns is set by calling the function\n\"clockevent_delta2ns()\" which returns a maximum value of LONG_MAX.\nFor a 32-bit machine LONG_MAX is equal to 0x7fffffff and in\nnanoseconds this equates to ~2.15 seconds. Hence, the maximum\nsleep time for a 32-bit machine is ~2.15 seconds, where as for\na 64-bit machine it will be many years.\n\nThis patch changes the type of max_delta_ns to be \"u64\" instead of\n\"unsigned long\" so that this variable is a 64-bit type for both 32-bit\nand 64-bit machines. It also changes the maximum value returned by\nclockevent_delta2ns() to KTIME_MAX. Hence this allows a 32-bit\nmachine to sleep for longer than ~2.15 seconds. Please note that this\npatch also changes \"min_delta_ns\" to be \"u64\" too and although this is\nunnecessary, it makes the patch simpler as it avoids to fixup all\ncallers of clockevent_delta2ns().\n\n[ tglx: changed \"unsigned long long\" to u64 as we use this data type\n \tthrough out the time code ]\n\nSigned-off-by: Jon Hunter \u003cjon-hunter@ti.com\u003e\nCc: John Stultz \u003cjohnstul@us.ibm.com\u003e\nLKML-Reference: \u003c1250617512-23567-3-git-send-email-jon-hunter@ti.com\u003e\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n" }, { "commit": "7d2f944a2b836c69a9d260a0a5f0d1720d57fdff", "tree": "67766d878c650ab7ac13d155081b9c745447e24e", "parents": [ "23af368e9a904f59256c27d371ce223d6cee0430" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Wed Nov 11 14:05:29 2009 +0000" }, "committer": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Fri Nov 13 20:46:23 2009 +0100" }, "message": "clocksource: Provide a generic mult/shift factor calculation\n\nMIPS has two functions to calculcate the mult/shift factors for clock\nsources and clock events at run time. ARM needs such functions as\nwell.\n\nImplement a function which calculates the mult/shift factors based on\nthe frequencies to which and from which is converted. The function\nalso has a parameter to specify the minimum conversion range in\nseconds. This range is guaranteed not to produce a 64bit overflow when\na value is multiplied with the calculated mult factor. The larger the\nconversion range the less becomes the conversion accuracy.\n\nProvide two inline wrappers which handle clock events and clock\nsources. For clock events the \"from\" frequency is nano seconds per\nsecond which corresponds to 1GHz and \"to\" is the device frequency. For\nclock sources \"from\" is the device frequency and \"to\" is nano seconds\nper second.\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nTested-by: Mikael Pettersson \u003cmikpe@it.uu.se\u003e\nAcked-by: Ralf Baechle \u003cralf@linux-mips.org\u003e\nAcked-by: Linus Walleij \u003clinus.walleij@stericsson.com\u003e\nCc: John Stultz \u003cjohnstul@us.ibm.com\u003e\nLKML-Reference: \u003c20091111134229.766673305@linutronix.de\u003e\n" }, { "commit": "23af368e9a904f59256c27d371ce223d6cee0430", "tree": "8d38ff75d731abc1182a331c2955b9c3c7025533", "parents": [ "3c5d92a0cfb5103c0d5ab74d4ae6373d3af38148" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Wed Nov 11 14:05:25 2009 +0000" }, "committer": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Fri Nov 13 20:46:23 2009 +0100" }, "message": "clockevents: Use u32 for mult and shift factors\n\nThe mult and shift factors of clock events differ in their data type\nfrom those of clock sources for no reason. u32 is sufficient for\nboth. shift is always \u003c\u003d 32 and mult is limited to 2^32-1 to avoid\n64bit multiplication overflows in the conversion.\n\nPreparatory patch for a generic mult/shift factor calculation\nfunction.\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nTested-by: Mikael Pettersson \u003cmikpe@it.uu.se\u003e\nAcked-by: Ralf Baechle \u003cralf@linux-mips.org\u003e\nAcked-by: Linus Walleij \u003clinus.walleij@stericsson.com\u003e\nCc: John Stultz \u003cjohnstul@us.ibm.com\u003e\nLKML-Reference: \u003c20091111134229.725664788@linutronix.de\u003e\n" }, { "commit": "6ff7041dbfeb3bd7dfe9aa67275c21199ef760d6", "tree": "c8897de7ba6c09d51d83557d981ced3da48bba61", "parents": [ "7e0c5086c172ecf8b0c2ad860b02a586967d17d0" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Fri Jul 10 14:57:05 2009 +0200" }, "committer": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Fri Jul 10 17:32:55 2009 +0200" }, "message": "hrtimer: Fix migration expiry check\n\nThe timer migration expiry check should prevent the migration of a\ntimer to another CPU when the timer expires before the next event is\nscheduled on the other CPU. Migrating the timer might delay it because\nwe can not reprogram the clock event device on the other CPU. But the\ncode implementing that check has two flaws:\n\n- for !HIGHRES the check compares the expiry value with the clock\n events device expiry value which is wrong for CLOCK_REALTIME based\n timers.\n\n- the check is racy. It holds the hrtimer base lock of the target CPU,\n but the clock event device expiry value can be modified\n nevertheless, e.g. by an timer interrupt firing.\n\nThe !HIGHRES case is easy to fix as we can enqueue the timer on the\ncpu which was selected by the load balancer. It runs the idle\nbalancing code once per jiffy anyway. So the maximum delay for the\ntimer is the same as when we keep the tick on the current cpu going.\n\nIn the HIGHRES case we can get the next expiry value from the hrtimer\ncpu_base of the target CPU and serialize the update with the cpu_base\nlock. This moves the lock section in hrtimer_interrupt() so we can set\nnext_event to KTIME_MAX while we are handling the expired timers and\nset it to the next expiry value after we handled the timers under the\nbase lock. While the expired timers are processed timer migration is\nblocked because the expiry time of the timer is always \u003c\u003d KTIME_MAX.\n\nAlso remove the now useless clockevents_get_next_event() function.\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n" }, { "commit": "eea08f32adb3f97553d49a4f79a119833036000a", "tree": "4e6af5185309d7abe49a8fa19634ea38582381e4", "parents": [ "cd1bb94b4a0531e8211a3774f17de831f8285f76" ], "author": { "name": "Arun R Bharadwaj", "email": "arun@linux.vnet.ibm.com", "time": "Thu Apr 16 12:16:41 2009 +0530" }, "committer": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Wed May 13 16:52:42 2009 +0200" }, "message": "timers: Logic to move non pinned timers\n\n* Arun R Bharadwaj \u003carun@linux.vnet.ibm.com\u003e [2009-04-16 12:11:36]:\n\nThis patch migrates all non pinned timers and hrtimers to the current\nidle load balancer, from all the idle CPUs. Timers firing on busy CPUs\nare not migrated.\n\nWhile migrating hrtimers, care should be taken to check if migrating\na hrtimer would result in a latency or not. So we compare the expiry of the\nhrtimer with the next timer interrupt on the target cpu and migrate the\nhrtimer only if it expires *after* the next interrupt on the target cpu.\nSo, added a clockevents_get_next_event() helper function to return the\nnext_event on the target cpu\u0027s clock_event_device.\n\n[ tglx: cleanups and simplifications ]\n\nSigned-off-by: Arun R Bharadwaj \u003carun@linux.vnet.ibm.com\u003e\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n" }, { "commit": "94df7de0289bc2df3d6e85cd2ece52bf42682f45", "tree": "b3f614b015adfb9574959687bb9b7ac4c884e23a", "parents": [ "7f22391cbe82a80a9f891d8bd10fc28ff248d1e2" ], "author": { "name": "Sebastien Dugue", "email": "sebastien.dugue@bull.net", "time": "Mon Dec 01 14:09:07 2008 +0100" }, "committer": { "name": "Ingo Molnar", "email": "mingo@elte.hu", "time": "Fri Jan 30 22:35:29 2009 +0100" }, "message": "hrtimers: allow the hot-unplugging of all cpus\n\nImpact: fix CPU hotplug hang on Power6 testbox\n\nOn architectures that support offlining all cpus (at least powerpc/pseries),\nhot-unpluging the tick_do_timer_cpu can result in a system hang.\n\nThis comes from the fact that if the cpu going down happens to be the\ncpu doing the tick, then as the tick_do_timer_cpu handover happens after the\ncpu is dead (via the CPU_DEAD notification), we\u0027re left without ticks,\njiffies are frozen and any task relying on timers (msleep, ...) is stuck.\nThat\u0027s particularly the case for the cpu looping in __cpu_die() waiting\nfor the dying cpu to be dead.\n\nThis patch addresses this by having the tick_do_timer_cpu handover happen\nearlier during the CPU_DYING notification. For this, a new clockevent\nnotification type is introduced (CLOCK_EVT_NOTIFY_CPU_DYING) which is triggered\nin hrtimer_cpu_notify().\n\nSigned-off-by: Sebastien Dugue \u003csebastien.dugue@bull.net\u003e\nCc: \u003cstable@kernel.org\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@elte.hu\u003e\n" }, { "commit": "320ab2b0b1e08e3805a3e1084a2f0eb1938d5d67", "tree": "1303d8ca53cca655425d512d65cc9ab043254b31", "parents": [ "0de26520c7cabf36e1de090ea8092f011a6106ce" ], "author": { "name": "Rusty Russell", "email": "rusty@rustcorp.com.au", "time": "Sat Dec 13 21:20:26 2008 +1030" }, "committer": { "name": "Rusty Russell", "email": "rusty@rustcorp.com.au", "time": "Sat Dec 13 21:20:26 2008 +1030" }, "message": "cpumask: convert struct clock_event_device to cpumask pointers.\n\nImpact: change calling convention of existing clock_event APIs\n\nstruct clock_event_timer\u0027s cpumask field gets changed to take pointer,\nas does the -\u003ebroadcast function.\n\nAnother single-patch change. For safety, we BUG_ON() in\nclockevents_register_device() if it\u0027s not set.\n\nSigned-off-by: Rusty Russell \u003crusty@rustcorp.com.au\u003e\nCc: Ingo Molnar \u003cmingo@elte.hu\u003e\n" }, { "commit": "7c1e76897492d92b6a1c2d6892494d39ded9680c", "tree": "ea04e1be252e176fe5a665a28fd1c26a562cb1fa", "parents": [ "d210baf53b699fc61aa891c177b71d7082d3b957" ], "author": { "name": "Venkatesh Pallipadi", "email": "venkatesh.pallipadi@intel.com", "time": "Wed Sep 03 21:36:50 2008 +0000" }, "committer": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Fri Sep 05 11:11:51 2008 +0200" }, "message": "clockevents: prevent clockevent event_handler ending up handler_noop\n\nThere is a ordering related problem with clockevents code, due to which\nclockevents_register_device() called after tickless/highres switch\nwill not work. The new clockevent ends up with clockevents_handle_noop as\nevent handler, resulting in no timer activity.\n\nThe problematic path seems to be\n\n* old device already has hrtimer_interrupt as the event_handler\n* new clockevent device registers with a higher rating\n* tick_check_new_device() is called\n * clockevents_exchange_device() gets called\n * old-\u003eevent_handler is set to clockevents_handle_noop\n * tick_setup_device() is called for the new device\n * which sets new-\u003eevent_handler using the old-\u003eevent_handler which is noop.\n\nChange the ordering so that new device inherits the proper handler.\n\nThis does not have any issue in normal case as most likely all the clockevent\ndevices are setup before the highres switch. But, can potentially be affecting\nsome corner case where HPET force detect happens after the highres switch.\nThis was a problem with HPET in MSI mode code that we have been experimenting\nwith.\n\nSigned-off-by: Venkatesh Pallipadi \u003cvenkatesh.pallipadi@intel.com\u003e\nSigned-off-by: Shaohua Li \u003cshaohua.li@intel.com\u003e\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@elte.hu\u003e\n" }, { "commit": "1595f452f3d8daa066bfd3ba4120754bed3329e1", "tree": "86fa49114c03e0f2dc7c7987b2a5be6adace140f", "parents": [ "b097976e8d6f6e6220161fa6b72b0798ce9f4f4c" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Sun Oct 14 22:57:45 2007 +0200" }, "committer": { "name": "Thomas Gleixner", "email": "tglx@inhelltoy.tec.linutronix.de", "time": "Sun Oct 14 22:57:45 2007 +0200" }, "message": "clockevents: introduce force broadcast notifier\n\nThe 64bit SMP bootup is slightly different to the 32bit one. It enables\nthe boot CPU local APIC timer before all CPUs are brought up. Some AMD C1E\nsystems have the C1E feature flag only set in the secondary CPU. Due to\nthe early enable of the boot CPU local APIC timer the APIC timer is\nregistered as a fully functional device. When we detect the wreckage during\nthe bringup of the secondary CPU, we need to force the boot CPU into\nbroadcast mode. \n\nAdd a new notifier reason and implement the force broadcast in the clock\nevents layer.\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n\n" }, { "commit": "de68d9b173ee657115dd0e584c2365b7954253a5", "tree": "d2fec5a10dc4dcceb2f702832cb6080a2ec6ff0f", "parents": [ "7f8033b76c8eea89dec9f658f4a31bcd4fe84bbb" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Fri Oct 12 23:04:05 2007 +0200" }, "committer": { "name": "Thomas Gleixner", "email": "tglx@inhelltoy.tec.linutronix.de", "time": "Fri Oct 12 23:04:05 2007 +0200" }, "message": "clockevents: Allow build w/o run-tine usage for migration purposes\n\nMigration aid to allow preparatory patches which introduce not yet\nused parts of clock events code.\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@elte.hu\u003e\nSigned-off-by: Arjan van de Ven \u003carjan@linux.intel.com\u003e\n\n" }, { "commit": "7f8033b76c8eea89dec9f658f4a31bcd4fe84bbb", "tree": "b7aafb8da60507b53701f9626b1bab2ff2f425a8", "parents": [ "782e3b3b3804c38d5130c7f21d7ec7bf6709023f" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Fri Oct 12 23:04:05 2007 +0200" }, "committer": { "name": "Thomas Gleixner", "email": "tglx@inhelltoy.tec.linutronix.de", "time": "Fri Oct 12 23:04:05 2007 +0200" }, "message": "clockevents: Remove unused inline function\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@elte.hu\u003e\nSigned-off-by: Arjan van de Ven \u003carjan@linux.intel.com\u003e\n\n" }, { "commit": "6ddfca9548d8ecc26096a30667423ba919109533", "tree": "9ba14a9d610439d724e199e3770967be544a5dad", "parents": [ "96ddbf504a05502800e7cbeb4d08abbcc206c51c" ], "author": { "name": "Miao Xie", "email": "miaox@cn.fujitsu.com", "time": "Fri Aug 10 13:01:09 2007 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Sat Aug 11 15:47:42 2007 -0700" }, "message": "timer: remove clockevents_unregister_notifier\n\nI find a function(clockevents_unregister_notifier) which is not called by\nanything in tree.\n\nSigned-off-by: Miao Xie \u003cmiaox@cn.fujitsu.com\u003e\nAcked-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "18de5bc4c1f1f1fa5e14f354a7603bd6e9d4e3b6", "tree": "cb0ff399fb3f368adecf213318e32a499ada6ff9", "parents": [ "93da56efcf8c6a111f0349f6b7651172d4745ca0" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Sat Jul 21 04:37:34 2007 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Sat Jul 21 17:49:15 2007 -0700" }, "message": "clockevents: fix resume logic\n\nWe need to make sure, that the clockevent devices are resumed, before\nthe tick is resumed. The current resume logic does not guarantee this.\n\nAdd CLOCK_EVT_MODE_RESUME and call the set mode functions of the clock\nevent devices before resuming the tick / oneshot functionality.\n\nFixup the existing users.\n\nThanks to Nigel Cunningham for tracking down a long standing thinko,\nwhich affected the jinxed VAIO.\n\n[akpm@linux-foundation.org: xen build fix]\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: john stultz \u003cjohnstul@us.ibm.com\u003e\nCc: Rusty Russell \u003crusty@rustcorp.com.au\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "93da56efcf8c6a111f0349f6b7651172d4745ca0", "tree": "4474ed05cf1d9d8558ecdf20964e06c1bfc278ef", "parents": [ "d4e3cc387ea1b74c3ad2ef2f6f5c05fd6fc314b8" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Sat Jul 21 04:37:33 2007 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Sat Jul 21 17:49:14 2007 -0700" }, "message": "clockevents: remove prototypes of removed functions\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: john stultz \u003cjohnstul@us.ibm.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "ce0be1273d1473a5a7b57bf0b4995b40c22d6b54", "tree": "c1473e9f0828ecaaa01f81cf18fb78d73e127c24", "parents": [ "58235413b24d5e5245685b84a4efe1ebc95f7886" ], "author": { "name": "Sergei Shtylyov", "email": "sshtylyov@ru.mvista.com", "time": "Tue May 08 00:31:55 2007 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Tue May 08 11:15:15 2007 -0700" }, "message": "clockchips.h: kernel-doc fix\n\nFix misnamed fields of \u0027struct clock_event_device\u0027 in the kernel-doc\ncomment. Convert the acronyms to uppercase, while at it...\n\nSigned-off-by: Sergei Shtylyov \u003csshtylyov@ru.mvista.com\u003e\nAcked-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "d316c57ff6bfad9557462b9100f25c6260d2b774", "tree": "f77a04aab5c39c416f52ff5ac9396da5a6b93759", "parents": [ "e05d723f98595b2f4d368f63636a997d98703304" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Fri Feb 16 01:28:00 2007 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Fri Feb 16 08:13:59 2007 -0800" }, "message": "[PATCH] clockevents: add core functionality\n\nArchitectures register their clock event devices, in the clock events core.\nUsers of the clockevents core can get clock event devices for their use. The\nclockevents core code provides notification mechanisms for various clock\nrelated management events.\n\nThis allows to control the clock event devices without the architectures\nhaving to worry about the details of function assignment. This is also a\npreliminary for high resolution timers and dynamic ticks to allow the core\ncode to control the clock functionality without intrusive changes to the\narchitecture code.\n\n[Fixes-by: Ingo Molnar \u003cmingo@elte.hu\u003e]\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@elte.hu\u003e\nCc: Roman Zippel \u003czippel@linux-m68k.org\u003e\nCc: john stultz \u003cjohnstul@us.ibm.com\u003e\nCc: Andi Kleen \u003cak@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" } ] }