On 05.09.2014 16:21, Makoto Harada wrote: > Dear expert > > Would someone please teach me how to confirm LOCALVERSION_AUTO config > effect ? > I built my kernel with LOCALVERSION_AUTO enabled, and boot my PC with > the kernel. > My expectation is that uname will return the kernel version with git > hush version added, > however I can not see it as shown below. > > [makoto@vostro ~]$ zcat /proc/config.gz |grep LOCALVERSION_AUTO > CONFIG_LOCALVERSION_AUTO=y > [makoto@vostro ~]$ uname -a > Linux vostro 3.2.0-makoto-0-dirty #5 SMP Fri Sep 5 22:32:22 JST 2014 > x86_64 GNU/Linux > > [makoto@vostro linux_mainline][v3.2]$ git rev-parse --verify HEAD > 805a6af8dba5dfdd35ec35dc52ec0122400b2610 > > Any insight would be highly appreciated. > > Kind Regards, > Makoto Harada > Hi Makoto, 805a6a is tagged as v3.2, and LOCALVERSION_AUTO matches git tags first as described in init/Kconfig: > This will try to automatically determine if the current tree is a > release tree by looking for git tags that belong to the current > top of tree revision. You might have left your changes to the kernel uncommited inside your git repository. These uncommited changes produce the -dirty string in your kernel name. The script at scripts/setlocalversion generates the version when you have set LOCALVERSION_AUTO=y, so you might also take a look there. - Julius _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies