From: Tony Breeds <tony@bakeyournoodle.com>
Date: Fri, 5 Mar 2004 14:16:43 +0800
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.6.4-rc2: scripts/modpost.c
Message-ID: <20040305061643.GH17221@bakeyournoodle.com>
Mail-Followup-To: lkml <linux-kernel@vger.kernel.org>
References: <20040304172923.6045760e.rddunlap@osdl.org> <20040304212440.30fc8674.randy.dunlap@verizon.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040304212440.30fc8674.randy.dunlap@verizon.net>
User-Agent: Mutt/1.3.28i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1048
Lines: 27

On Thu, Mar 04, 2004 at 09:24:40PM -0800, Randy.Dunlap wrote:
 
> The comment and code certainly don't match, and your patch makes sense
> to me.  However, I can't reproduce the problem that you describe.
> 
> I built the kernel image and modules in "www.osdl.org/264rc2/build1",
> and all *.mod.c and *.ko ended up there with no problems.
> Then I modified modpost.c (from 2.6.4-rc1, without your patch) to
> print the "stripped" module names (without the trailing ".o")
> and saw a list like this:
> modpost: stripped mod.name=[fs/jfs/jfs]
> 
> so where are the parent directory names that are causing problems
> for you coming from?

When building external modules.

Yours Tony

        linux.conf.au       http://lca2005.linux.org.au/
	Apr 18-23 2005      The Australian Linux Technical Conference!

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/