Messages in this thread | | | From | Ajay Garg <> | Date | Sat, 2 Oct 2021 09:01:38 +0530 | Subject | Recommended way to do kernel-development for static modules |
| |
Hello All,
Let's say, I want to make a simple printk change to drivers/pci/bus.c, compile it, load it, test it.
Now, since bus.o is built as a result of CONFIG_PCI=y in drivers/pci/Makefile, so this module is statically built, and as a result doing a "make M=drivers/pci" does-not-pick-up-the-change / have-any-effect.
Doing a simple "make" takes too long, everytime for even a trivial change.
So, what is the recommended way to do kernel-development for static modules?
Will be grateful for pointers.
Thanks and Regards, Ajay
| |