Messages in this thread | | | Date | Wed, 8 Apr 2009 14:41:42 +0800 | Subject | Re: Linux 2.6.30-rc1 | From | Jike Song <> |
| |
On Wed, Apr 8, 2009 at 8:20 AM, Linus Torvalds <torvalds@linux-foundation.org> wrote: > > So the two week merge window has closed, and just as well - because we had > a lot of changes. As usual. Certainly I had no urges to keep the window > open to get those last remaining few megabytes of patches.. > > The changes follow roughly the same pattern they have before: one third > crap (that is, "staging" - the new random drivers that aren't really ready > to be merged properly but get into the tree in the hope that they'll get > better some day), one third real drivers, and one third "rest". > > And just to not break a new tradition, there's a few new filesystems in > this release too: > > - "nilfs2" has been brewing for a long while, and is another > log-structured filesystem that does snapshotting. Just google for > 'nilfs2' for more details. > > - "exofs" implements a filesystem on top of an external object store > (ie not a traditional storage of a linear array of anonymous blocks, > but a "smart" disk that does objects). See > > Documentation/filesystems/exofs.txt > > for some details. > > - fscache/cachefiles is not really a filesystem, but infrastructure to do > caching of remote filesystems in the local filesystem, and NFS and AFS > have been updated to be able to use it. > > I'm personally hoping that we'll run out of filesystems rather than > continue this new tradition indefinitely, but we'll see. > > But we've got older filesystems updated too: btrfs hopefully uses less > stack space and is usable with a 4k stack, reiserfs got some updates, and > a lot of other filesystems got minor refreshes. The ext3 changes are small > enough to not show up in any dirstat, but hey, I think the fsync latency > changes are interesting and probably more relevant to lots of people than > most of the other changes. > > Other? Arch updates - amainly rm, powerpc, sh and x86. Firmware updates. > And lots and lots of driver updates, including some more core > suspend/resume changes (hopefully the last really fundamental ones). > > Go out and try it, > > Linus
There is no way to build if one has CONFIG_SERIAL_MAX3100 selected to be 'y' or 'm' - there is not max3100.c at all...
-- Thanks, Jike -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |