On Fri, Jul 06, 2018 at 09:56:23AM +0200, Geert Uytterhoeven wrote: > Hi Simon, > > On Thu, Jul 5, 2018 at 5:55 PM Simon Horman <ho...@verge.net.au> wrote: > > On Wed, Jul 04, 2018 at 01:43:33PM +0200, Geert Uytterhoeven wrote: > > > This allows to derive the kernel flavor from the kernel version at > > > runtime. > > > > For my edification could you expand on what this is used for? > > With this, the kernel version (as printed during boot, and returned by > e.g. "uname -r") will be something like > > 4.18.0-rc3-shmobile-02146-gd2f8e14acc47b8ea > > instead of > > dmesg-4.18.0-rc3 > > which makes it easy to differentiate them from > > 4.18.0-rc3-koelsch-02146-gd2f8e14acc47b8ea > 4.17.0-rc1-rcar2-initrd-00547-g19c9f87b5c449c23-dirty > > which are built from my personal configs for Koelsch resp. R-Car Gen2 > with initrd. > > > > Signed-off-by: Geert Uytterhoeven <geert+rene...@glider.be> > > > > --- a/arch/arm/configs/shmobile_defconfig > > > +++ b/arch/arm/configs/shmobile_defconfig > > > @@ -1,3 +1,4 @@ > > > +CONFIG_LOCALVERSION="-shmobile" > > We already have > > CONFIG_LOCALVERSION="-arm64-renesas" > > in arch/arm64/configs/renesas_defconfig, to differentiate kernels built > from that config with kernels built from arm64 defconfig (which set it to > "-arm64" in my local tree). > > All of this makes it easy to keep e.g. a collection of boot logs using > "dmesg > dmesg-$(uname -r)", and compare them.
Thanks, sounds good!
