The 2.6.29 merge window closes

[Posted January 11, 2009 by corbet]

Linus has released 2.6.29-rc1 and closed the merge window for this development cycle. "I wanted to release -rc1 with time enough that by the time I'm on my way to LCA next weekend, we'd have an -rc2 too, and the worst fallout from -rc1 would be fixed. But I know all you nice developers have been oh-so-careful, and there won't be any fall-out, will there? I'm sure -rc1 is going to be fine." As usual, there is a lot of new stuff in this release; the changes that stand out the most, though, will be the addition of the squashfs read-only compressed filesystem, Btrfs (in a development mode), and kernel mode setting for Intel graphics hardware. See the full changelog for lots of details.

Is CUSE merged?

Posted Jan 12, 2009 13:10 UTC (Mon) by Tuxie (guest, #47191) [Link] (2 responses)

In the changelog I see things like these:
* "fuse: separate out fuse_conn_init() from new_conn()" [...] "This will be used by CUSE."
* "Add fuse_ prefix to request_send*() and get_root_inode() as some of those functions will be exported for CUSE."
* "fuse: implement ioctl support" [...] "Unrestricted ioctl will be used by CUSE."

Was CUSE merged this time or was the kernel only prepared for CUSE merging in 2.6.30?

(For those of you who don't know, CUSE is the FUSE equivalent for character devices in userspace, which means that we will among other things be able to route /dev/dsp calls to ALSA/pulseaudio/JACK without LD_PRELOAD hacks)

Is CUSE merged?

Posted Jan 12, 2009 14:40 UTC (Mon) by rahulsundaram (subscriber, #21946) [Link]

If CUSE was merged, I am pretty sure you will see it explicitly mentioned in the changelog and LWN summary. For now, it appears that some preparatory work has been done.

Is CUSE merged?

Posted Jan 12, 2009 16:01 UTC (Mon) by corbet (editor, #1) [Link]

No CUSE for 2.6.29. Some of the prerequisites are there now, though.