<?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 - David Miller</title>
 <link>http://www.kerneltrap.org/taxonomy/term/577/0</link>
 <description></description>
 <language>en-local</language>
<item>
 <title>what is an APE memory?</title>
 <link>http://www.kerneltrap.org/node/59573</link>
 <description>&lt;div class=&quot;taxonomy-images&quot;&gt;&lt;/div&gt;&lt;!-- google_ad_section_start --&gt;&lt;p&gt;Hey I was going through Broadcom Tigon 3 drivers code and I see that APE memory is mapped using pic_ioremap_bar(pdev,BAR_2).&lt;/p&gt;
&lt;p&gt;I couldn&#039;t any information in the broadcom datasheet about APE memory. What is an APE memory and what exactly it is used for?&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://lxr.linux.no/linux+v2.6.33/drivers/net/tg3.c#L14499&quot; title=&quot;http://lxr.linux.no/linux+v2.6.33/drivers/net/tg3.c#L14499&quot;&gt;http://lxr.linux.no/linux+v2.6.33/drivers/net/tg3.c#L14499&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;br /&gt;
Santhosh Kokala&lt;/p&gt;
&lt;!-- google_ad_section_end --&gt;</description>
 <comments>http://www.kerneltrap.org/node/59573#comments</comments>
 <category domain="http://www.kerneltrap.org/David_Miller">David Miller</category>
 <category domain="http://www.kerneltrap.org/taxonomy/term/171">Linux kernel</category>
 <pubDate>Thu, 13 May 2010 06:16:08 +0000</pubDate>
 <dc:creator>skokal01</dc:creator>
 <guid isPermaLink="false">59573 at http://www.kerneltrap.org</guid>
</item>
<item>
 <title>Quote: Time Is Often What Shakes Out Problems</title>
 <link>http://www.kerneltrap.org/Quote/Time_Is_Often_What_Shakes_Out_Problems</link>
 <description>&lt;!-- google_ad_section_start --&gt;&lt;p&gt;&quot;I like to make sure some time passes between when a fix goes into Linus&#039;s tree and when I push it into -stable because time is often what shakes out the last remaining problems introduced by some change no matter how seemingly obvious the patch is.&quot;&lt;/p&gt;
&lt;!-- google_ad_section_end --&gt;</description>
 <comments>http://www.kerneltrap.org/Quote/Time_Is_Often_What_Shakes_Out_Problems#comments</comments>
 <category domain="http://www.kerneltrap.org/David_Miller">David Miller</category>
 <category domain="http://www.kerneltrap.org/taxonomy/term/1283">Linux. quote</category>
 <category domain="http://www.kerneltrap.org/taxonomy/term/1137">David Miller</category>
 <category domain="http://www.kerneltrap.org/taxonomy/term/1094">linux-kernel</category>
 <pubDate>Sun, 15 Jun 2008 19:52:47 +0000</pubDate>
 <dc:creator>Jeremy</dc:creator>
 <guid isPermaLink="false">16294 at http://www.kerneltrap.org</guid>
</item>
<item>
 <title>Quote: We Read Over The Code And Learned How It Worked</title>
 <link>http://www.kerneltrap.org/Quote/We_Read_Over_The_Code_And_Learned_How_It_Worked</link>
 <description>&lt;!-- google_ad_section_start --&gt;&lt;p&gt;&quot;Look at anyone who is extremely nimble with the kernel, and ask them what they worked on to get going with development.  Did Andrew Morton fixup whitespace errors when he was starting to become familiar with the tree?  Did I?&lt;/p&gt;
&lt;!-- google_ad_section_end --&gt;&lt;p&gt;&lt;a href=&quot;http://www.kerneltrap.org/Quote/We_Read_Over_The_Code_And_Learned_How_It_Worked&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.kerneltrap.org/Quote/We_Read_Over_The_Code_And_Learned_How_It_Worked#comments</comments>
 <category domain="http://www.kerneltrap.org/Andrew_Morton">Andrew Morton</category>
 <category domain="http://www.kerneltrap.org/David_Miller">David Miller</category>
 <category domain="http://www.kerneltrap.org/Kernel_Janitors">Kernel Janitors</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/1137">David Miller</category>
 <category domain="http://www.kerneltrap.org/taxonomy/term/1094">linux-kernel</category>
 <pubDate>Fri, 30 May 2008 14:14:57 +0000</pubDate>
 <dc:creator>Jeremy</dc:creator>
 <guid isPermaLink="false">16216 at http://www.kerneltrap.org</guid>
</item>
<item>
 <title>Bugs And Bureaucracy</title>
 <link>http://www.kerneltrap.org/Linux/Bugs_And_Bureaucracy</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;A thread on the Linux Kernel mailing list discussed the process in place for reporting, bisecting and fixing bugs.  In response to a suggestion that some of the issues could be solved by introducing new procedures, Al Viro retorted, &quot;&lt;i&gt;we&#039;ve got ourselves a developing beaurocracy.  As in &#039;more and more ways of generating activity without doing anything even remotely useful&#039;.  Complete with tendency to operate in the ways that make sense only to bureaucracy in question and an ever-growing set of bylaws...&lt;/i&gt;&quot;  Later in the thread, David Miller agreed and noted that ,&quot;&lt;i&gt;the resulting &#039;bureaucracy&#039; or whatever you want to call it is perceived to undercut the very thing that makes the Linux kernel fun to work on.  It&#039;s still largely free form, loose, and flexible.  And that&#039;s a notable accomplishment considering how much things have changed.  That feeling is why I got involved in the first place, and I know it&#039;s what gets other new people in and addicted too.&lt;/i&gt;&quot;&lt;/p&gt;
&lt;p&gt;Andrew Morton tried to return the discussion to its original topic, &quot;&lt;i&gt;the problem we&#039;re discussing here is the apparently-large number of bugs which are in the kernel, the apparently-large number of new bugs which we&#039;re adding to the kernel, and our apparent tardiness in addressing them.&lt;/i&gt;&quot;  Al noted that some of the problem is that git is so efficient at merging code, &quot;&lt;i&gt;the patches going in during a merge (especially for a tree that collects from secondaries) are not visible enough.  And it&#039;s too late at that point, since one has to do something monumentally ugly to get Linus revert a large merge.  On the scale of Great IDE Mess in 2.5...&lt;/i&gt;&quot;  Another suggestion was made to replace bugzilla with something better, to which Andrew replied, &quot;&lt;i&gt;swapping out bugzilla for something else wouldn&#039;t help.  We&#039;d end up with lots of people ignoring a good bug tracking system just like they were ignoring a bad one.&lt;/i&gt;&quot;&lt;/p&gt;
&lt;!-- google_ad_section_end --&gt;&lt;p&gt;&lt;a href=&quot;http://www.kerneltrap.org/Linux/Bugs_And_Bureaucracy&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.kerneltrap.org/Linux/Bugs_And_Bureaucracy#comments</comments>
 <category domain="http://www.kerneltrap.org/Al_Viro">Al Viro</category>
 <category domain="http://www.kerneltrap.org/Andrew_Morton">Andrew Morton</category>
 <category domain="http://www.kerneltrap.org/bugs">bugs</category>
 <category domain="http://www.kerneltrap.org/taxonomy/term/411">bugzilla</category>
 <category domain="http://www.kerneltrap.org/David_Miller">David Miller</category>
 <category domain="http://www.kerneltrap.org/development_process">development process</category>
 <category domain="http://www.kerneltrap.org/Linux">Linux</category>
 <category domain="http://www.kerneltrap.org/news/linux">Linux news</category>
 <pubDate>Mon, 14 Apr 2008 22:35:52 +0000</pubDate>
 <dc:creator>Jeremy</dc:creator>
 <guid isPermaLink="false">15985 at http://www.kerneltrap.org</guid>
</item>
<item>
 <title>Quote: Not Investing the Necessary Time</title>
 <link>http://www.kerneltrap.org/Quote/Not_Investing_the_Necessary_Time</link>
 <description>&lt;!-- google_ad_section_start --&gt;&lt;p&gt;&quot;Every single argument you make that supports why you should not be investing the necessary time into the bug applies equally to the very developers you are so quick to quip at and want help from.&quot;&lt;/p&gt;
&lt;!-- google_ad_section_end --&gt;</description>
 <comments>http://www.kerneltrap.org/Quote/Not_Investing_the_Necessary_Time#comments</comments>
 <category domain="http://www.kerneltrap.org/David_Miller">David Miller</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/1137">David Miller</category>
 <category domain="http://www.kerneltrap.org/taxonomy/term/1094">linux-kernel</category>
 <pubDate>Mon, 14 Apr 2008 16:34:59 +0000</pubDate>
 <dc:creator>Jeremy</dc:creator>
 <guid isPermaLink="false">15984 at http://www.kerneltrap.org</guid>
</item>
<item>
 <title>Quote: A Fart In A Spacesuit</title>
 <link>http://www.kerneltrap.org/Quote/A_Fart_In_A_Spacesuit</link>
 <description>&lt;!-- google_ad_section_start --&gt;&lt;p&gt;&quot;About as cool as a fart in a spacesuit.&quot;&lt;/p&gt;
&lt;!-- google_ad_section_end --&gt;</description>
 <comments>http://www.kerneltrap.org/Quote/A_Fart_In_A_Spacesuit#comments</comments>
 <category domain="http://www.kerneltrap.org/David_Miller">David Miller</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/1137">David Miller</category>
 <category domain="http://www.kerneltrap.org/taxonomy/term/1094">linux-kernel</category>
 <pubDate>Tue, 01 Apr 2008 12:48:16 +0000</pubDate>
 <dc:creator>Jeremy</dc:creator>
 <guid isPermaLink="false">15890 at http://www.kerneltrap.org</guid>
</item>
<item>
 <title>Quote: Don&#039;t Panic</title>
 <link>http://www.kerneltrap.org/Quote/Dont_Panic</link>
 <description>&lt;!-- google_ad_section_start --&gt;&lt;p&gt;&quot;It&#039;s ascii art I took it from someone&#039;s signature 12 years ago, it&#039;s meant to be the guy on the cover of some of the editions of the Hitchhikers Guide to the Galaxy by Douglas Adams. Don&#039;t Panic! :-)&quot;&lt;/p&gt;
&lt;!-- google_ad_section_end --&gt;</description>
 <comments>http://www.kerneltrap.org/Quote/Dont_Panic#comments</comments>
 <category domain="http://www.kerneltrap.org/David_Miller">David Miller</category>
 <category domain="http://www.kerneltrap.org/Linux">Linux</category>
 <category domain="http://www.kerneltrap.org/oops">Oops</category>
 <category domain="http://www.kerneltrap.org/quote">quote</category>
 <category domain="http://www.kerneltrap.org/taxonomy/term/1137">David Miller</category>
 <category domain="http://www.kerneltrap.org/taxonomy/term/1094">linux-kernel</category>
 <pubDate>Thu, 07 Feb 2008 13:21:52 +0000</pubDate>
 <dc:creator>Jeremy</dc:creator>
 <guid isPermaLink="false">15440 at http://www.kerneltrap.org</guid>
</item>
<item>
 <title>Quote: Quality of the Bug Report</title>
 <link>http://www.kerneltrap.org/Quote/Quality_of_the_Bug_Report</link>
 <description>&lt;!-- google_ad_section_start --&gt;&lt;p&gt;&quot;This case is a good example to use the next time a stupid thread starts up about bug reports not being looked into.  To me it seems clearly more a matter of the quality of the bug report.&quot;&lt;/p&gt;
&lt;!-- google_ad_section_end --&gt;</description>
 <comments>http://www.kerneltrap.org/Quote/Quality_of_the_Bug_Report#comments</comments>
 <category domain="http://www.kerneltrap.org/bugs">bugs</category>
 <category domain="http://www.kerneltrap.org/David_Miller">David Miller</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/1137">David Miller</category>
 <category domain="http://www.kerneltrap.org/taxonomy/term/1094">linux-kernel</category>
 <pubDate>Tue, 27 Nov 2007 03:44:42 +0000</pubDate>
 <dc:creator>Jeremy</dc:creator>
 <guid isPermaLink="false">14883 at http://www.kerneltrap.org</guid>
</item>
<item>
 <title>Quote: Glacial Development Pace</title>
 <link>http://www.kerneltrap.org/Quote/Glacial_Development_Pace</link>
 <description>&lt;!-- google_ad_section_start --&gt;&lt;p&gt;&quot;Yeah, if you develop at the glacial pace Solaris does, don&#039;t add any features to cyclics or work on scalability improvements, sure it can be bug free and untouched for 6 years.&quot;&lt;/p&gt;
&lt;!-- google_ad_section_end --&gt;</description>
 <comments>http://www.kerneltrap.org/Quote/Glacial_Development_Pace#comments</comments>
 <category domain="http://www.kerneltrap.org/David_Miller">David Miller</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/1137">David Miller</category>
 <category domain="http://www.kerneltrap.org/taxonomy/term/1094">linux-kernel</category>
 <pubDate>Thu, 15 Nov 2007 02:40:09 +0000</pubDate>
 <dc:creator>Jeremy</dc:creator>
 <guid isPermaLink="false">14803 at http://www.kerneltrap.org</guid>
</item>
<item>
 <title>Bug Fixing and Kernel Code Quality</title>
 <link>http://www.kerneltrap.org/Linux/Bug_Fixing_and_Kernel_Code_Quality</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;&quot;&lt;i&gt;This is the listing of the open bugs that are relatively new, around 2.6.22 and up. They are vaguely classified by specific area,&lt;/i&gt;&quot; Natalie Protasevich said, posting a current &lt;a href=&quot;http://kerneltrap.org/mailarchive/linux-netdev/2007/11/13/407804&quot;&gt;list of bugs&lt;/a&gt; each linking to an appropriate &lt;a href=&quot;http://bugzilla.kernel.org/&quot;&gt;bugzilla.kernel.org&lt;/a&gt; entry.  Andrew Morton reviewed the list, noting &quot;&lt;i&gt;no response from developers&lt;/i&gt;&quot; in response to many of the bugs.  David Miller pointed out that in some cases this wasn&#039;t true, referring to 46 bug fixes queued in his networking tree and another 10 already pushed upstream, &quot;&lt;i&gt;when someone like me is bug fixing full time, I take massive offense to the impression you&#039;re trying to give especially when it&#039;s directed at the networking.  So turn it down a notch Andrew.&lt;/i&gt;&quot;  Andrew wasn&#039;t convinced, &quot;&lt;i&gt;first we need to work out whether we have a problem.  If we do this, then we can then have a think about what to do about it.  I tried to convince the 2006 KS attendees that we have a problem and I resoundingly failed.  People seemed to think that we&#039;re doing OK.&lt;/i&gt;&quot;  He continued:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;&quot;This is not a minor matter.  If the kernel _is_ slowly deteriorating then this won&#039;t become readily apparent until it has been happening for a number of years.  By that stage there will be so much work to do to get us back to an acceptable level that it will take a huge effort.  And it will take a long time after that for the kerel to get its reputation back.  So it is important that we catch deterioration *early* if it is happening.&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/Bug_Fixing_and_Kernel_Code_Quality&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.kerneltrap.org/Linux/Bug_Fixing_and_Kernel_Code_Quality#comments</comments>
 <category domain="http://www.kerneltrap.org/Andrew_Morton">Andrew Morton</category>
 <category domain="http://www.kerneltrap.org/bugs">bugs</category>
 <category domain="http://www.kerneltrap.org/David_Miller">David Miller</category>
 <category domain="http://