From mboxrd@z Thu Jan 1 00:00:00 1970 From: greg@kroah.com (Greg KH) Date: Mon, 23 Jan 2012 10:15:27 -0800 Subject: what is the "+" sigh in the modules folder name? In-Reply-To: References: <9362dcb8461f9de4a7036f960553747f@basementcode.com> <20120123173424.GB27125@kroah.com> Message-ID: <20120123181527.GA27664@kroah.com> To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org On Mon, Jan 23, 2012 at 12:40:41PM -0500, Robert P. J. Day wrote: > On Mon, 23 Jan 2012, Greg KH wrote: > > > On Tue, Jan 24, 2012 at 12:25:20AM +0700, Mulyadi Santosa wrote: > > > Hi... > > > > > > On Mon, Jan 23, 2012 at 23:15, Christopher Harvey > > > wrote: > > > > I have a path on system called: > > > > '/lib/modules/2.6.37+/' > > > > It used to be called: > > > > '/lib/modules/2.6.37/' > > > > > > Hm strange. You said you have the kernel source, right? Can you show > > > us about ten top lines of the Makefile in the main kernel source > > > directory? > > > > > > I am suspecting there is "+" character in the extraversion..but that > > > needs to be checked.... > > > > No, it just means you have a "modified" kernel tree, that is not reall > > 2.6.37, you have changed it somehow. The build system asks git about > > this when building the kernel. > > you sure? i thought that if it was a modified working tree, you'd > get the "-dirty" qualifier added, not just a "+". Try it and see :)