-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said:
| Currently we have two patchsets - one generic OpenWrt-patchset for | 2.6.28-kernels (located here: | https://svn.openwrt.org/openwrt/trunk/target/linux/generic-2.6/patches-2.6.28/), | some little s3c46xx-related patches | (https://svn.openwrt.org/openwrt/trunk/target/linux/s3c24xx/patches-2.6.28/ | (just minor changes)) and the big Openmoko-"diff-blob" between | andy-tracking and the vanilla branch. Some patches of both sets apply | on the same source or functionality - that's why we fixed | andy-tracking at some point and solved the conflicting parts manually | to get both sets applied on the vanilla source. Generally I think it works better to absorb worthwhile patches into our tree or if they'll wear it upstream of us and avoid bitrot. But I was surprised how many patches you apply... I realise you have to take care about MIPS / big endian but still, there's several patches on netfilter and mtd. That's even scarier than our Big Scary Patchset :-) - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmEhfAACgkQOjLpvpq7dMp5CQCcCKwkUgAm4QAWRBOQlhqPyH7N NAkAnAiU+vqYt81vRn22evNbDtpeet0z =E3/O -----END PGP SIGNATURE----- _______________________________________________ devel mailing list devel@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/devel
