Messages in this thread | | | Subject | RE: [PATCH] Prevent modpost from looking for a .cmd file for a static library linked into a module | Date | Fri, 10 Oct 2008 18:15:01 -0700 | From | "Ashutosh Naik" <> |
| |
On Tue, 7 Oct 2008 11:26:15 -0700 "Ashutosh Naik" <ashutosh@chelsio.com> wrote:
>> >> This patch prevents modpost to look for a .cmd file when a module is >> linked with a static library >> >> Signed-off-by: Ashutosh Naik <ashutosh.naik@gmail.com>
>What is the reason for this change?
>Presumably there is some user-observeable behaviour which it corrects? >What is it, and under what circumstances does it occur?
This fixes a Compile time Warning, whenever a static library is linked into a kernel module. MODPOST tries to look for a ".<modulename>.cmd" file to look for its dependencies, but that file doesn't exist or get generated for static libraries.
<snip>
>The patch was wordwrapped. I fixed that and queued it for sending to >Sam. Please send me an updated, complete changelog, thanks.
Thanks for fixing the wordwrap.
Here is the changelog: This fixes a Compile time Warning, whenever a static library is linked into a kernel module. MODPOST tries to look for a ".<modulename>.cmd" file to look for its dependencies, but that file doesn't exist or get generated for static libraries.
Many Thanks, Ashutosh
| |