<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.kerneltrap.org"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>KernelTrap - Jesper Juhl</title>
 <link>http://www.kerneltrap.org/taxonomy/term/242/0</link>
 <description></description>
 <language>en-local</language>
<item>
 <title>Quote: The Burden of Debugging</title>
 <link>http://www.kerneltrap.org/Quote/The_Burden_of_Debugging</link>
 <description>&lt;!-- google_ad_section_start --&gt;&lt;p&gt;&quot;The way I see it, the burden of debugging and fixing bugs is mainly on the developers of the code that breaks. You can&#039;t blame users for using the code, triggering bugs and then reporting the breakage.  Users who report bugs are doing us all a great service regardless of their ability or willingness to do more work than just the initial report.&quot;&lt;/p&gt;
&lt;!-- google_ad_section_end --&gt;</description>
 <comments>http://www.kerneltrap.org/Quote/The_Burden_of_Debugging#comments</comments>
 <category domain="http://www.kerneltrap.org/bugs">bugs</category>
 <category domain="http://www.kerneltrap.org/taxonomy/term/242">Jesper Juhl</category>
 <category domain="http://www.kerneltrap.org/Linux">Linux</category>
 <category domain="http://www.kerneltrap.org/quote">quote</category>
 <category domain="http://www.kerneltrap.org/taxonomy/term/1228">Jesper Juhl</category>
 <category domain="http://www.kerneltrap.org/taxonomy/term/1094">linux-kernel</category>
 <pubDate>Fri, 11 Apr 2008 22:01:34 +0000</pubDate>
 <dc:creator>Jeremy</dc:creator>
 <guid isPermaLink="false">15967 at http://www.kerneltrap.org</guid>
</item>
<item>
 <title>Linux: Moving 4K Stacks Forward</title>
 <link>http://www.kerneltrap.org/Linux/Moving_4K_Stacks_Forward</link>
 <description>&lt;div class=&quot;taxonomy-images&quot;&gt;&lt;a href=&quot;/news/linux&quot; class=&quot;taxonomy-image-links&quot;&gt;&lt;img src=&quot;http://kerneltrap.org/files/category_pictures/K-Linux.gif&quot; alt=&quot;Linux news&quot; title=&quot;Linux news&quot;  width=&quot;75&quot; height=&quot;75&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;!-- google_ad_section_start --&gt;&lt;p&gt;In a series of 5 patches, Jesper Juhl propsed moving 4K stacks from a debug feature to a non-debug feature, defaulting it to be enabled in the -mm tree.  He referred back to a lengthy &lt;a href=&quot;http://lkml.org/lkml/2007/7/11/294&quot;&gt;earlier discussion&lt;/a&gt; in which he had proposed making 4K stacks the default in the mainline kernel, then added:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;&quot;Based on the comments in that thread I conclude that 4KSTACKS are not really  considered a debug-only feature any longer, but the time is not right (yet) to make them the default - and it&#039;s certainly not yet the time to get rid of 8K stacks.&quot;&lt;/p&gt;
&lt;p&gt;&quot;In that thread I promised to provide some patches that would lift 4KSTACKS out of debug-only feature status, which is what the first two patches in this series do.  I also said I would provide a patch to make 4KSTACKS &#039;default y&#039; to get more testing, but restrict that patch to -mm - that&#039;s the fifth patch in this series.  Patches 3 &amp;amp; 4 in this series move the config option out of the Kernel hacking menu and into Processor types and features&quot;.&lt;/p&gt;&lt;/blockquote&gt;
&lt;!-- google_ad_section_end --&gt;&lt;p&gt;&lt;a href=&quot;http://www.kerneltrap.org/Linux/Moving_4K_Stacks_Forward&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.kerneltrap.org/Linux/Moving_4K_Stacks_Forward#comments</comments>
 <category domain="http://www.kerneltrap.org/-mm">-mm</category>
 <category domain="http://www.kerneltrap.org/4k_stacks">4k stacks</category>
 <category domain="http://www.kerneltrap.org/8k_stacks">8k stacks</category>
 <category domain="http://www.kerneltrap.org/debug">debug</category>
 <category domain="http://www.kerneltrap.org/taxonomy/term/242">Jesper Juhl</category>
 <category domain="http://www.kerneltrap.org/news/linux">Linux news</category>
 <pubDate>Thu, 16 Aug 2007 20:42:16 +0000</pubDate>
 <dc:creator>Jeremy</dc:creator>
 <guid isPermaLink="false">14194 at http://www.kerneltrap.org</guid>
</item>
<item>
 <title>Linux:  Translating Kernel Documentation</title>
 <link>http://www.kerneltrap.org/node/8365</link>
 <description>&lt;div class=&quot;taxonomy-images&quot;&gt;&lt;a href=&quot;/news/linux&quot; class=&quot;taxonomy-image-links&quot;&gt;&lt;img src=&quot;http://kerneltrap.org/files/category_pictures/K-Linux.gif&quot; alt=&quot;Linux news&quot; title=&quot;Linux news&quot;  width=&quot;75&quot; height=&quot;75&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;!-- google_ad_section_start --&gt;&lt;p&gt;The translation of a some kernel documentation into Japanese led to a discussion as to whether or not it was appropriate to include translated documentation with the kernel source code.  One concern that was expressed was that as the number of included translations grows, so would the size of the kernel.  Another concern was the liklihood that as time passes the various translations might become out of date.  Jesper Juhl suggested one workaround, &quot;&lt;i&gt;since the common language of most kernel contributors is english I personally feel that we should stick to just that one language in the tree and then perhaps keep translations on a website somewhere. So the authoritative docs stay in the tree, in english, so that as many contributors as possible can read and update them.&lt;/i&gt;&quot;&lt;/p&gt;
&lt;p&gt;Greg KH noted that there were a number of files in the kernel that change infrequently and that he would like to see included, &quot;&lt;i&gt;I really do want to see a translated copy of the HOWTO, stable-api-nonsense.txt, and possibly a few other files in the main kernel tree (SubmittingPatches, CodingStyle, and SubmittingDrivers might all be good canidates for this.)  These files change relatively infrequently (the HOWTO file has had only 7 changes in 1 and 1/2 years, and they were very minor ones) and should be easy for the translators to keep up with.&lt;/i&gt;&quot;&lt;/p&gt;
&lt;!-- google_ad_section_end --&gt;&lt;p&gt;&lt;a href=&quot;http://www.kerneltrap.org/node/8365&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.kerneltrap.org/node/8365#comments</comments>
 <category domain="http://www.kerneltrap.org/documentation">documentation</category>
 <category domain="http://www.kerneltrap.org/Greg_KH">Greg KH</category>
 <category domain="http://www.kerneltrap.org/HOWTO">HOWTO</category>
 <category domain="http://www.kerneltrap.org/taxonomy/term/241">Japanese</category>
 <category domain="http://www.kerneltrap.org/taxonomy/term/242">Jesper Juhl</category>
 <category domain="http://www.kerneltrap.org/Linux">Linux</category>
 <category domain="http://www.kerneltrap.org/taxonomy/term/217">translation</category>
 <category domain="http://www.kerneltrap.org/news/linux">Linux news</category>
 <pubDate>Mon, 11 Jun 2007 10:36:38 +0000</pubDate>
 <dc:creator>Jeremy</dc:creator>
 <guid isPermaLink="false">8365 at http://www.kerneltrap.org</guid>
</item>
<item>
 <title>Linux:  Cleaning Up Per The Kernel Coding Style</title>
 <link>http://www.kerneltrap.org/node/5100</link>
 <description>&lt;div class=&quot;taxonomy-images&quot;&gt;&lt;a href=&quot;/news/linux&quot; class=&quot;taxonomy-image-links&quot;&gt;&lt;img src=&quot;http://kerneltrap.org/files/category_pictures/K-Linux.gif&quot; alt=&quot;Linux news&quot; title=&quot;Linux news&quot;  width=&quot;75&quot; height=&quot;75&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;!-- google_ad_section_start --&gt;&lt;p&gt;Jesper Juhl &lt;a href=&quot;http://kerneltrap.org/mailarchive/1/message/64343/thread&quot;&gt;submitted a small patch&lt;/a&gt; to bring the &lt;code&gt;kernel/module.c&lt;/code&gt; source file closer in line with the kernel&#039;s &lt;a href=&quot;http://kerneltrap.org/files/Jeremy/CodingStyle.txt&quot;&gt;CodingStyle&lt;/a&gt; document.  Specifically, he quoted from the CodingStyle document, &quot;&lt;i&gt;don&#039;t put multiple statements on a single line unless y