Hi Christopher, From my knowledge it because of in linux-2.6.37/Makefile In my case content of Lantiq_UGW_5.x/linux/Makefile #head Lantiq_UGW_5.x/linux/Makefile VERSION = 2 PATCHLEVEL = 6 SUBLEVEL = 32 EXTRAVERSION = .32 NAME = Man-Eating Seals of Antiquity # *DOCUMENTATION* This EXTRAVERSION get added to Kernel build path # Read KERNELRELEASE from include/config/kernel.release (if it exists) KERNELRELEASE = $(shell cat include/config/kernel.release 2> /dev/null) KERNELVERSION = $(VERSION).$(PATCHLEVEL).$(SUBLEVEL)$(EXTRAVERSION) On My system on provide the following command. #uname -r #2.6.32.32 # If you check the EXTRAVERSION you will find the reason of '+' Or Some were in the linux-2.6.37/Makefile you might be appending some extra FLAGS or environment variable to KERNELVERSION. Read the linux-2.6.37/Makefile for details under the following line. # Build the kernel release string Please try to echo this "KERNELVERSION" during compilation of kernel. -Anand Moon ________________________________ From: Christopher Harvey <chris@basementcode.com> To: kernelnewbies@kernelnewbies.org Sent: Tuesday, January 24, 2012 8:46 PM Subject: Re: what is the "+" sigh in the modules folder name? On 23.01.2012 15:53, Robert P. J. Day wrote:
On Tue, 24 Jan 2012, Graeme Russ wrote:
It would be worth testing if a checkout of a tag (say 3.2.0) plus a local commit causes '+' and 'dirty'
i think "dirty" only shows up if you have local, uncommitted changes. but i should probably verify that.
I had a local commits when I compiled the kernel. I should have mentioned that in my original email. _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies