LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Linux 2.6.25-rc1
Date: Sun, 10 Feb 2008 16:44:29 -0800 (PST)	[thread overview]
Message-ID: <alpine.LFD.1.00.0802101603240.2920@woody.linux-foundation.org> (raw)


Ok, it's a bloody large -rc (as was 24-rc1, for that matter), probably 
because the 2.6.24 release cycle dragged out, so people had a lot of 
things pending.

The full diff is something like 11MB and 1.4M lines of diffs, with the 
bulk of the stuff being in architecture updates and drivers.

Just to have some fun, I did trivial statistics, and of the 1.4M lines of 
diffs, about 38% - 530k lines - were in architecture files (400k+ lines of 
diffs in arch/, 100k+ lines of diffs in include/asm-*), and another big 
chunk is in drivers (including sound) at about 44% - 610k lines - of 
changes.

The rest comes in much smaller, but still noticeable is networking (8% - 
110k lines), with filesystems at 4%, and documentation at about 2%. The 
remaining crumbles being spread out mostly over block layer, crypto, 
kernel core, and security layer updates (ie SElinux and smack).

[ Just to make it more obvious how driver and architecture-dominated the 
  kernel changelogs are: just the network driver changes were 200kloc, and 
  even just infiniband - which came way behind not just networking 
  drivers, but also DVB, SCSI, char and ide - generated more lines of code 
  changed than the "core" kernel code under the kernel/ subdirectory. 

  And that's despite the fact that the "core" code was actually under a 
  fairly active merge cycle, with a lot of namespace- and scheduling-
  related stuff. ]

Now, some of that is files moving about and other reorganizations (SH and 
to a lesser degree sparc starting to merge 32-bit and 64-bit 
architectures), but most of it really is just the normal flood of changes 
and new driver or platform support.

The full shortlog is half a meg in size (and the diffstat is even bigger), 
so I won't be including that here, but some things that may be worth 
pointing out not because they are big in line sizes, but because they have 
potential to be noticed by more people:

 - the intel graphics driver is starting to do suspend/resume natively 
   (ie even without X support), which is a welcome sign of the times and 
   may help some people. It helped on my laptop.

 - Other suspend/resume changes in device access ordering etc, and the 
   usual ACPI changes means that we really want reports from people about 
   this all even if you don't have intel graphics.

 - Lots of cleanups from the x86 merge (making more and more use of common 
   files), but also the big page attribute stuff is in and caused a fair 
   amount of churn, and while most of the issues should have been very 
   obvious and all got fixed, this is definitely one of those things that 
   we want a lot of very wide testing of to make sure nothing regressed.

 - fair number of changes to things like the legacy IDE drivers too, and a 
   totally new driver for the very common PCIE version of the Intel e1000 
   network card etc.

 - .. and I've probably totally forgotten about tons of other stuff I 
   should have mentioned, but the point is that not only do we have lots 
   of new core, we do have a fair amout of changes to basic stuff that can 
   actually affect perfectly bog-standard hardware setups.

So give it all a good testing. 

		Linus

             reply	other threads:[~2008-02-11  0:45 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-11  0:44 Linus Torvalds [this message]
2008-02-11  1:36 ` Sergio Luis
2008-02-11  1:47 ` Linux 2.6.25-rc1 , syntax error near unexpected token `;' Mr. James W. Laferriere
2008-02-11  7:02   ` Ray Lee
2008-02-11 13:29     ` [patch] " Oleg Verych
2008-02-11 13:26   ` Sam Ravnborg
2008-02-12  3:37     ` Mr. James W. Laferriere
2008-02-11  3:14 ` Linux 2.6.25-rc1 Gene Heskett
2008-02-11  7:39 ` Brice Goglin
2008-02-11 15:16   ` Arjan van de Ven
2008-02-11 11:19 ` parisc - error: 'VMALLOC_START' undeclared Domenico Andreoli
2008-02-11 12:06   ` Adrian Bunk
2008-02-11 13:31 ` Linux 2.6.25-rc1 Sam Ravnborg
2008-02-11 16:17   ` Mike Frysinger
2008-02-11 16:47   ` [PATCH] kbuild: fix make V=1 Sam Ravnborg
2008-02-11 23:38     ` Oleg Verych
2008-02-12  8:56       ` Sam Ravnborg
2008-02-12  9:25         ` Oleg Verych
2008-02-12 15:07           ` Mike Frysinger
2008-02-12 15:49             ` Oleg Verych
2008-02-12 16:18               ` Mike Frysinger
2008-02-12 16:42                 ` Oleg Verych
2008-02-12 20:01           ` Sam Ravnborg
2008-02-11 21:46 ` Linux 2.6.25-rc1 Torsten Kaiser
2008-02-11 22:15   ` Andrew Morton
2008-02-11 22:48     ` Stefan Richter
2008-02-13 19:17     ` Torsten Kaiser
2008-02-12  8:18 ` [ata crash] " Ingo Molnar
2008-02-12 15:14   ` Arjan van de Ven
2008-02-13  9:01     ` Ingo Molnar
2008-02-13  9:20       ` [libata-dev #upstream-fixes] pata_legacy: don't call ata_host_detach() after initialization failure Tejun Heo
2008-02-13  9:24         ` Ingo Molnar
2008-02-15 18:52         ` Jeff Garzik
2008-02-13  9:51   ` [ata crash] Re: Linux 2.6.25-rc1 Tejun Heo
2008-02-21  2:33     ` Tejun Heo
2008-02-21  7:12       ` Ingo Molnar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.1.00.0802101603240.2920@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Linux 2.6.25-rc1' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).