kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: safarin87@gmail.com (Safarin)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Practical way to rename kernel-release on custom kernel
Date: Thu, 10 Jul 2014 23:28:39 +0800	[thread overview]
Message-ID: <20140710152839.GA30830@archlinux.domain.name> (raw)

Hi Guys,

This question might be very easy for all of you. But seem this is
kernelnewbies mailing list. I need to ask this question.

I in the middle of learning to build custom kernel and my question is
how to have custom name for kernel version.

$ uname -r

I can see custom kernel print message.

>From what I read, we can change inside .config 
CONFIG_LOCALVERSION="-ARCH"
will produce the kernel release naming something like this.
3.16.0-rc3-ARCH

But somehow, when I try to install the modules

$make modules_install 

I can see makefile create folder inside the lib/modules with naming
3.16.0-rc3-ARCH-00570-g110e430

110e430 is actually commit id and I check that naming is generated by 
#define UTS_RELEASE "3.16.0-rc3-ARCH-00570-g110e430" in the
"include/generated/utsrelease.h" header  which will
overwrite "include/config/kernel.release".

Back to the question, what is the practical way to naming the kernel
release for custom kernel? with additional question for understanding
more from where that utsrelease came from?

Thanks,

Regards,
Safarin

             reply	other threads:[~2014-07-10 15:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-10 15:28 Safarin [this message]
2014-07-10 15:56 ` Practical way to rename kernel-release on custom kernel AYAN KUMAR HALDER
2014-07-11  0:47 ` shhuiw
2014-07-11  7:24   ` shhuiw
2014-07-11 18:08     ` Safarin
2014-07-11  3:03 ` Anil Shashikumar Belur

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140710152839.GA30830@archlinux.domain.name \
    --to=safarin87@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).