-
Simon Rose authored
The original e3 build installed the module.Makefile in the module source directory, and then runs (essentially) ``` $ make -C module -f module.Makefile ARGS ``` However, there is no real need for it to copy it there instead of simply using that makefile from the parent directory. This simplifies a bit of the junk that gets added around during the build process.
Simon Rose authoredThe original e3 build installed the module.Makefile in the module source directory, and then runs (essentially) ``` $ make -C module -f module.Makefile ARGS ``` However, there is no real need for it to copy it there instead of simply using that makefile from the parent directory. This simplifies a bit of the junk that gets added around during the build process.
Code owners
Assign users and groups as approvers for specific file changes. Learn more.