mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jike Song <albcamus@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.30-rc1
Date: Wed, 8 Apr 2009 14:41:42 +0800	[thread overview]
Message-ID: <df9815e70904072341ic2a8621s12994ab4f4ba7fb3@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0904071700170.4583@localhost.localdomain>

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

  parent reply	other threads:[~2009-04-08  6:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08  0:20 Linus Torvalds
2009-04-08  2:26 ` Kevin Bowling
2009-04-08  5:09   ` Christian Kujau
2009-04-08  4:27 ` Linux 2.6.30-rc1 boot failure on ia64 w/ QLA12160. Bisected Robin Holt
2009-04-08  7:33   ` David Woodhouse
2009-04-08  7:36     ` David Woodhouse
2009-04-08 11:41       ` Robin Holt
2009-04-08  8:31   ` David Woodhouse
2009-04-09 15:43     ` Jaswinder Singh Rajput
2009-04-09 15:59       ` David Woodhouse
2009-04-08  5:37 ` Linux 2.6.30-rc1 Robin Holt
2009-04-08  5:54   ` Michael Chan
2009-04-08  6:25     ` Robin Holt
2009-04-08  7:12       ` Linux 2.6.30-rc1 tg3 endian issues with MAC addresses on BCM5701. Bisected Robin Holt
2009-04-13 17:57         ` Matt Carlson
2009-04-13 20:15           ` Robin Holt
2009-04-13 20:43             ` David Miller
2009-04-13 20:44           ` David Miller
2009-04-08  6:07 ` Linux 2.6.30-rc1 Michal Simek
2009-04-08  6:41 ` Jike Song [this message]
2009-04-08 11:33 ` Morten P.D. Stevens

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=df9815e70904072341ic2a8621s12994ab4f4ba7fb3@mail.gmail.com \
    --to=albcamus@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®