Hi Javier, On Tue, Jan 24, 2012 at 8:30 AM, Javier Martinez Canillas <martinez.javier@xxxxxxxxx> wrote: > On Mon, Jan 23, 2012 at 8:52 PM, Graeme Russ <graeme.russ@xxxxxxxxx> wrote: >> On 01/24/2012 05:15 AM, Greg KH wrote: >>> 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 >>>>>> <chris@xxxxxxxxxxxxxxxx> 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 :) >> >> >From what I can tell, the '+' means you are building source which includes >> upstream commits after the last tag in the tree >> > > Well that commits not necessarily are upstream ;-) > > It only means that are commits after the last tag. It would be worth testing if a checkout of a tag (say 3.2.0) plus a local commit causes '+' and 'dirty' Regards, Graeme _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
