Kernel Traffic
Latest | Archives | People | Topics 		Wine
Latest | Archives | People | Topics 		GNUe
Latest | Archives | People | Topics
Czech
Home | News | RSS Feeds | Mailing Lists | Authors Info | Mirrors | Stalled Traffic
 

Kernel Traffic #314 For 8 Jun 2005

By Zack Brown

Table Of Contents

Mailing List Stats For This Week

We looked at 1881 posts in 11MB. See the Full Statistics.

There were 638 different contributors. 240 posted more than once. The average length of each message was 99 lines.

The top posters of the week were: The top subjects of the week were:
69 posts in 317KB by ingo molnar
67 posts in 367KB by jeff garzik
47 posts in 226KB by bill huey (hui)
44 posts in 240KB by nick piggin
43 posts in 338KB by adrian bunk
 330 posts in 2MB for "rt patch acceptance"
66 posts in 294KB for "playing with sata ncq"
41 posts in 218KB for "[patch] real-time preemption, -rt-2.6.12-rc4-v0.7.47-06"
38 posts in 233KB for "2.6.12-rc5-mm1"
36 posts in 262KB for "numa aware slab allocator v3"

These stats generated by mboxstats version 2.8

1. Linux 2.6.12-rc5-mm1 Released

25 May 2005 - 31 May 2005 (55 posts) Archive Link: "2.6.12-rc5-mm1"

Topics: Clustering, I2O, Kernel Release Announcement, Kexec, Version Control

People: Andrew Morton

Andrew Morton announced Linux 2.6.12-rc5-mm1, saying:

ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc5/2.6.12-rc5-mm1/

2. ALSA Development Switches To git

27 May 2005 - 29 May 2005 (16 posts) Archive Link: "ALSA official git repository"

Topics: Sound: ALSA

People: Jaroslav Kysela, Linus Torvalds

Jaroslav Kysela said:

I created new git tree for the ALSA project at:

rsync://rsync.kernel.org/pub/scm/linux/kernel/git/perex/alsa.git

This tree is intended for pushing ALSA changes to Linus and will follow the kernel development/release cycles once synced for the first time. It contains all latest patches from ALSA 1.0.9 now.

I will create another repository (probably alsa-devel.git) for testing the latest ALSA driver changes (suited for the -mm kernels).

Linus Torvalds pointed out that Jaroslav's conversion to git left blank lines at the start of each commit message, which interfered with some web-based git repo browsers.

There was some discussion that perhaps git should strip off extraneous whitespace, but the bottom line was that log messages could be pure binary data, and so stripping some of that off would only serve to corrupt it in those cases. In the end, Jaroslav just reconverted his tree without the extra spaces.

Jaroslav's tree had another anomaly - the "Signed-off-by" lines did not put the true author on top, as they should. At one point Linus explained:

the algorithm is:
- the email author, _or_ if there is one, the top "From:" in the body.

And the rule is that you never remove (or add to) an existing From:, since the author doesn't change from being passed around.

Put another way: authorship is very different from sign-off. The sign-off gets stacked, the authorship is constant, and thus the rules are different.

Also, authorship is more important than sign-off-ship, so authorship goes at the top, while sign-offs go at the bottom.

Later, Jaroslav reconverted his tree again, to conform to this logic.

3. Linux 2.6.11.11 Released

27 May 2005 - 29 May 2005 (2 posts) Archive Link: "Linux 2.6.11.11"

Topics: USB

People: Chris Wright, Lee Revell, Linus Torvalds

Chris Wright announced Linux 2.6.11.11, saying:

We (the -stable team) are announcing the release of the 2.6.11.11 kernel.

The diffstat and short summary of the fixes are below.

I'll also be replying to this message with a copy of the patch between 2.6.11.10 and 2.6.11.11, as it is small enough to do so.

The updated 2.6.11.y git tree can be found at:

rsync://rsync.kernel.org/pub/scm/linux/kernel/git/gregkh/linux-2.6.11.y.git

and can be browsed at the normal kernel.org git web browser:

www.kernel.org/git/

One of the fixes was for a USB oop, and the fix was attributed to Gregor Jasny. Lee Revell pointed out that the true author was Karsten Wiese. Lee said, "Someone must have signed off on it incorrectly, presumably the person who submitted it for -stable." Chris confirmed, "Yes, you are right, the git commit scripts culled that author info from the person who submitted it to -stable." Linus Torvalds remarked:

Side note: the patch-applicator scripts will, if the first line of the email body is of the form "^From: xxxx", and there's exactly one '@' sign on that line, then it will assume that it's supposed to be the author info, and use that instead of the "From: " line in the header of the email.

So when passing on stuff from others, that's always the preferred way to do it. A lot of people already follow this convention, and it might even be documented somewhere.

4. Possible GPL Violation By Panda

30 May 2005 (6 posts) Archive Link: "Possible GPL Violation"

People: Carlos Silva, Måns Rullgård

Carlos Silva said, "the company that i work for is going to buy a pair of Panda Gatedefenders 8200 that are linux based. To start, they never told us or mention on their site (as far as i searched) the use of linux in their product. Another thing is that they don't give us root access nor any other type of local access to the box besides the http page the appliance have to be managed. The thing is that i asked for the kernel source they use in the system and they said they can't give it since they have some proprietary code in it, as far as i understood." Måns Rullgård said the company was not obligated to give full access to the machine. But he did say, "If they use some modules of their own writing, the general agreement seems to be that they don't need to release the source code to those. They should still give you the kernel source they used, along with any patches they may have applied."

Carlos said he was aware of these requirements, but reiterated, "The thing is that they don't give me anything. They only sell me the appliance, nothing more. :(" Måns replied, "All too common. You should begin by kindly pointing out what their obligations are, and if they fail to comply, switch to a harsher tone, and post your correspondence in a public place. I'm not certain that lkml is the proper place for this, but it may be the only place we have. If all else fails, slashdot them. That will probably also fail, but at least you can enjoy watching other people call them names." Carlos replied, "i aslready asked them in kindly and harsher tone, so it's a dead end here."

Giuseppe Bilotta suggested going to http://www.gpl-violations.org/.

5. GCC 4 Cannot Compile Linux 2.4

30 May 2005 (3 posts) Archive Link: "[2.4 patch] document that gcc 4 is not supported"

People: Adrian Bunk, Mikael Pettersson

Adrian Bunk said:

gcc 4 is not supported for compiling kernel 2.4, and I don't see any compelling reason why kernel 2.4 should ever be adapted to gcc 4.

This patch documents this fact.

Mikael Pettersson pointed out that "This is redundant. Any attempt to compile vanilla 2.4 with gcc4 will fail with compilation errors." But Adrian replied:

Without this patch, your screen is flooded with warnings and errors when accidentially trying to compile kernel 2.4 with gcc 4.

With this patch, the same happens, but the last lines contain the explanation

#error Sorry, your GCC is too recent for kernel 2.4

6. libata Developer Guide Updated; Ongoing Development Using git

30 May 2005 (1 post) Archive Link: "libata dev guide updated"

People: Jeff Garzik

Jeff Garzik said:

Just made a run through the libata docs, updating them for the latest hooks and filling in missing details like locking/context documentation. I've been playing with lulu.com self-publishing, and published this newly updated libata Developer's Guide there as a short book (92 pages):

http://www.lulu.com/content/130446

I think the muddy road on the front cover is apropos :)

This guide continues to be open source -- just run "make pdfdocs" in the kernel source tree.

A PDF of the book is available for free on lulu.com or at http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata.pdf or by running "make pdfdocs" (or "make psdocs", "make htmldocs", ...).

The source code for the guide is in the kernel source tree, with new additions in the 'docs' branch of

rsync://rsync.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git

7. Linux 2.4.31-rc2 Released; 2.4 Development Migrating To git

31 May 2005 (1 post) Archive Link: "Linux 2.4.31-rc2"

People: Marcelo Tosatti

Marcelo Tosatti announced Linux 2.4.31-rc2, saying:

It incorporates two small hardening fixes from Willy's -hotfix tree.

v2.4.31 will follow shortly.

PS: beginning from v2.4.31 the v2.4 tree will reside in a GIT repository.

8. Linux 2.4.31 Released

31 May 2005 (1 post) Archive Link: "linux-2.4.31 released"

People: Marcelo Tosatti

Marcelo Tosatti announced Linux 2.4.31, with no changes from 2.4.31-rc2. Presumably all development is now done in git.

 

 

 

 

 

 

Sharon And Joy
 

Kernel Traffic is grateful to be developed on a computer donated by Professor Greg Benson and Professor Allan Cruse in the Department of Computer Science at the University of San Francisco. This is the same department that invented FlashMob Computing. Kernel Traffic is hosted by the generous folks at kernel.org. All pages on this site are copyright their original authors, and distributed under the terms of the GNU General Public License version 2.0.