Re: Linux 2.5.19

Jason Lunz (lunz@reflexsecurity.com)
Wed, 29 May 2002 15:42:32 -0400


In mlist.linux-kernel, you wrote:
> <kai@tp1.ruhr-uni-bochum.de>
> o kbuild: Figure out flags independently from pass
> o ISDN/CAPI: Move methods from capi_driver to capi_ctr
> o kbuild: Simplify rule for just building one subdir
> o kbuild: Use consistently FORCE instead of dummy
> o drivers/video/matrox/matroxfb_accel.c: Explicitly export symbols.
> o ISDN/CAPI: Cleanup /proc/capi
> o ISDN: CAPI: Remove unused capi_driver::driver_read_proc
> o ISDN/CAPI: Have hardware driver alloc struct capi_drv
> o ISDN/CAPI: Export callbacks for CAPI drivers directly
> o ISDN/CAPI: Remove struct capi_driver
> o kbuild: built-in and modules in one pass
> o kbuild: Normal sources should not include <linux/compile.h>
> o kbuild: Add EXTRA_TARGETS variable
> o kbuild: Remove remaining O_TARGET in drivers/*/Makefile
> o kbuild: Don't overwrite Rules.make's first_rule
> o kbuild: beautify Makefile / Rules.make...
> o kbuild: Group together descending/linking in drivers/*
> o kbuild: Build targets locally
> o kbuild: Provide correct 'make some/dir/file.[iso]'
> o kbuild: Hand merge link order change form driverfs update.

Are these purely patches to kbuild 1 or are they the beginning of a
gradual migration to kbuild 2?

-- 
Jason Lunz			Reflex Security
lunz@reflexsecurity.com		http://www.reflexsecurity.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/