Which patches for 2.6.30
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): mailman.1.1244170801.2227.users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Hi!
I want to use nilfs as the root file system of the next version of SIMPLUX (a Gentoo-Linux based distribution for pen-drives). Shutdown by now works cleanly. (I had some troubles in the past ...)
My question is: Which patches do I need to include the most current version of nilfs in the upcoming final release of kernel 2.6.30? nilfs will be directly included in the kernel (no module). Is it possible to have a single patch that does it all?
Greetings, Michael
Hi!
Quoted 10 lines · Michael Niederle
Hi!
I want to use nilfs as the root file system of the next version of SIMPLUX (a Gentoo-Linux based distribution for pen-drives). Shutdown by now works cleanly. (I had some troubles in the past ...)
My question is: Which patches do I need to include the most current version of nilfs in the upcoming final release of kernel 2.6.30? nilfs will be directly included in the kernel (no module). Is it possible to have a single patch that does it all?
Basically, you should use the in-tree version without applying any additional patches because known bugfixes are included in the kernel 2.6.30 and the remaining patches are experimental.
But, you can try the latest version available on the experimental branch or for-next branch in nilfs2.git:
git://git.kernel.org/pub/scm/linux/kernel/git/ryusuke/nilfs2.git
(As you can see in
http://git.kernel.org/?p=linux/kernel/git/ryusuke/nilfs2.git;a=shortlog;h=experimental
the for-next branch is included in the experimental branch)
If you already have a git clone of linus' tree, you can add those branches like:
$ cd linux-2.6 $ git remote add nilfs2 git://git.kernel.org/pub/scm/linux/kernel/git/ryusuke/nilfs2.git $ git branch nilfs2-experimental nilfs2/experimental (or nilfs2/for-next) $ git checkout nilfs2-experimental
Otherwise, you can get it directly by:
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/ryusuke/nilfs2.git $ cd nilfs2 $ git checkout experimental
And, you can create the single patch by:
$ cd nilfs2 $ git diff master...experimental > ~/v2.6.30-nilfs2-experimental.diff
Note that the for-next branch and the experimental branch are frequently "rebased" and this may confuse their existing branches.
Cheers,
Ryusuke Konishi