[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1108151600400.22798@chino.kir.corp.google.com>
Date: Mon, 15 Aug 2011 16:06:04 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: Pavel Roskin <proski@....org>
cc: linux-kernel@...r.kernel.org
Subject: Re: Suppressing a plus from setlocalversion
On Mon, 15 Aug 2011, Pavel Roskin wrote:
> Hello!
>
> There is one annoyance in the build system that I cannot work around.
That's surprising since you actually state the workaround, i.e. using
LOCALVERSION= with make, yourself.
> Before I attempt hacking the code, I'd like to make sure I'm not
> missing anything obvious.
>
> Suppose that I have a kernel version 3.1-rc2. I want to test some patch
> for some code that is compiled as a module. I change the code and
> create a patch with STGit. I recompile the modules, install them by
> "make module_install", unload the module I patched, load it again
> and find that there is no effect from my change. It turns out that the
> modules were installed to "/lib/modules/3.1.0-rc2+" and the plus was
> added by scripts/localversion because the source tree is now modified.
>
Yes, because the kernel you've produced is no longer 3.1.0-rc2, it is
modified. If you want to do something else locally, then you can always
use LOCALVERSION=.
The + was added to stop falsely identifying kernels as a specific version
when they are modified by default. Sorry if you forget to override it
sometimes.
--
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