On Wed, Sep 01, 2021 at 05:34:36PM +0200, Krish Jain wrote: > Oh ok, thanks Greg. I only attempted to use "make CCFLAGS=-Werror W=1 > M=drivers/staging/android/" as that's the command Bryan used earlier > and it worked. > > "As for your patch, I built the driver using: > > $ make CCFLAGS=-Werror W=1 M=drivers/staging/android" > > > Can you tell me why this is the case? Again, it depends on your kernel configuration file as to what will, or will not, be built. If you have some things set as modules, they can be built as a module, but the ashmem code can not be built as a module, so you would never build it if you did the above line. Here, look at this sequence, starting with a tree that does nothing if I do a simple 'make' in it, as the whole kernel is already built, and ashmem is enabled in the kernel configuration $ grep ASHMEM .config CONFIG_ASHMEM=y $ make $ So, let's change the time stamp on the ashmem.c file and see what gets built if you use the M= option: $ touch drivers/staging/android/ashmem.c $ make M=drivers/staging/android MODPOST drivers/staging/android/Module.symvers $ Nothing gets built as ashmem is NOT a module, and M= only builds any modules in the directory you specified. But, if you tell make to just build the whole subdirectory, no matter what the setting is, it will be built: $ make drivers/staging/android/ CALL scripts/checksyscalls.sh CALL scripts/atomic/check-atomics.sh DESCEND objtool CC drivers/staging/android/ashmem.o AR drivers/staging/android/built-in.a $ So that's the difference, "M=" builds modules in that directory, but if you tell it to build the subdir, everything in there that needs to be built, will be built. Be careful about your kernel configuration, that is the key for what will, and will not, be built. Perhaps you should look at the book, "Linux Kernel in a Nutshell" that is free online. It talks all about building and configuring a kernel. Parts of it are out of date, but the general ideas are good. hope this helps, greg k-h
