1) Create new kernel image
2) Compile the modules
3) Install the modules
After all of above commands were finished, i just have to copy some files to /boot directory (System.map, .config, and bzImage), rename it to reflect the kernel version and assign the correct symlink (System.map -> System.map-126.96.36.199, config -> config-188.8.131.52, vmlinuz -> vmlinuz-184.108.40.206).
Why do i choose this kind of scheme? Well, in my opinion, it's easier if we gave the version number on the file, so when we want to delete the old kernel, we can just do it by deleting the file that matches with the number, so if you have just upgraded to 220.127.116.11 and you want to delete 2.6.19, you can just type rm *2.6.19* in /boot, /lib/modules, and /usr/src (make sure that your new 18.104.22.168 kernel works first before deleting this files, since it's irreversible).
One thing that makes me curious is that there was a new question when i ran make oldconfig, which didn't suppose to be there, since it's a -stable kernel. Usually, a -stable kernel only consists of security update or bug fixes, but not new feature(s) which should be done in the next final kernel release. The question was about new feature to support 2/3 button emulation on Macintosh computers. When i traced back to the Changelog, i found this information:
Author: Soeren Sonnenburg <email@example.com>
Date: Thu Feb 8 14:20:38 2007 -0800
enable mouse button 2+3 emulation for x86 macs
As macbook/macbook pro's also have to live with a single mouse button the following patch just enables the Macintosh device drivers menu in Kconfig + adds the macintosh dir to the obj-* to make macbook* users happy (who use exactly that since months....
Signed-off-by: Soeren Sonnenburg <firstname.lastname@example.org>
Cc: Benjamin Herrenschmidt <email@example.com>
Cc: Paul Mackerras <firstname.lastname@example.org>
Cc: Dmitry Torokhov <email@example.com>
Signed-off-by: Andrew Morton <firstname.lastname@example.org>
Signed-off-by: Greg Kroah-Hartman <email@example.com>
I guess that it won't bite too much if this feature is being added and something goes wrong, so they just put this updates on -stable kernel (even though it's disabled by default if you enabled them in the configuration phase since i'm not using Macintosh).