[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8A71B368A89016469F72CD08050AD3340397130C@maui.asicdesigners.com>
Date: Fri, 10 Oct 2008 18:15:01 -0700
From: "Ashutosh Naik" <ashutosh@...lsio.com>
To: "Andrew Morton" <akpm@...ux-foundation.org>
Cc: <linux-kernel@...r.kernel.org>, <stable@...nel.org>,
<rusty@...tcorp.com.au>, "Karen Xie" <kxie@...lsio.com>,
"Sam Ravnborg" <sam@...nborg.org>
Subject: RE: [PATCH] Prevent modpost from looking for a .cmd file for a static library linked into a module
On Tue, 7 Oct 2008 11:26:15 -0700
"Ashutosh Naik" <ashutosh@...lsio.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@...il.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists