On Wed, Mar 20, 2013 at 2:22 AM, Luis R. Rodriguez <mcgrof@xxxxxxxxxxxxxxxx> wrote: > From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxxxxxxxx> > > This patch series deals with the project that aims at > backporting the Linux kernel [0]. If you don't care > for that, at least read this and patch #1, the rest > you can nuke. > > Ben reports compat_ namespace is already taken by the > kernel, and while this is slightly true, I rather just > deal with this now and avoid any future issues. > > I've chosen backport_. Any nay's? > > I've broken this set for easier review to one per kernel > backported. Each patch is test compiled with ckmake [1] > for kernels 2.6.24 - 3.9. I've then test compiled all this > against compat-drivers-2013-03-15, which sucks in Ethernet, > 802.11 Bluetooth, and DRM video drivers against linux-next > tag next-20130315 and it all went fine for all kernels > 2.6.24 - 3.9. > > I suppose the next set here, if we really are adamant about > any possible namespace issues (is it necessary?) is to use > include/linux/backport/ instead of include/linux/compat/ and > likewise rename the compat module to backports as with > COMPAT_* macros. > > I'm sending these as RFCs in hopes to get reviews / testing > prior to any radical change, but more importantly in hopes > anyone who cares for maintaining a Linux distribution will > review. > > [0] https://backports.wiki.kernel.org > [1] https://git.kernel.org/cgit/linux/kernel/git/mcgrof/compat.git/tree/bin/ckmake I heard no one cry, so pushed. Luis -- To unsubscribe from this list: send the line "unsubscribe backports" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
