(given that, in some cases, you don't have the freedom to select the kernel version you want when building a new image, this idea might not have much value, but what the heck.)
is there any value to creating a new directory of kernel patches created against the latest git pull of the kernel? that is, currently, under target/linux/generic-2.6/, there are patch directories patches-2.6.22, patches-2.6.23 and patches-2.6.24. but there's nothing for the latest "git pull" in case someone wants to try to build an image with that latest pull. there's a simple solution to this. for each major kernel version that comes out, create a new patches directory for it (in this case, patches-2.6.24), after which you immediately create a sibling directory patches-git, whose contents are initially just symlinks back to each patch file under patches-2.6.24. obviously, that git patches directory will be perfectly relevant at the beginning but, as commits are checked into the git repo, those patch files will, little by little, start to fail to patch. as each one fails, you replace the symlink in patches-git/ with an actual text file that's been tweaked to apply properly. (and, while you're at it, maybe even fix any offset and fuzz issues.) this is a fairly simple way to keep up with the git kernel, but the problem is that i don't see, under "make menuconfig", how to select my version of the kernel. i'm guessing that, in some cases, this selection is made for me based on my selection of target system. in cases like that, the git patches won't do any good. but i think it would be useful to be able to build test images against the latest git pull of the kernel, so that any errors are identified ASAP. thoughts? rday -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA Home page: http://crashcourse.ca Fedora Cookbook: http://crashcourse.ca/wiki/index.php/Fedora_Cookbook ======================================================================== _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
