From: Chris Clayton <chris2553@googlemail.com>
To: linux-kbuild@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>, mmarek@suse.cz
Subject: Re: linux-3.9.0-rc1+: Output from "make kernelrelease"contains incorrect data
Date: Mon, 01 Apr 2013 10:28:42 +0100 [thread overview]
Message-ID: <5159534A.1070500@googlemail.com> (raw)
In-Reply-To: <513B8FA7.9040200@googlemail.com>
Ping!
This is still happening with 3.9-rc5.
[chris:~/kernel/linux]$ make bzImage
...
Kernel: arch/x86/boot/bzImage is ready (#14)
[chris:~/kernel/linux]$ make kernelrelease
scripts/kconfig/conf --silentoldconfig Kconfig
3.9.0-rc5
[chris:~/kernel/linux]$ make kernelrelease
3.9.0-rc5
I'm assuming that the output from 'make kernelrelease' should be the
string that represents the kernel release and only that string.
Chris
On 03/09/13 19:38, Chris Clayton wrote:
> In Linus' current tree, the first time the command "make kernelrelease"
> is run after building a kernel, the output contains some unwanted text.
> Subsequent uses of the command produce the expected output. This appears
> to be a regression - 3.8.2 does not have this problem.
>
> This is easily demonstrated from the command line by the following:
>
> <build the kernel>
> ...
> System is 2311 kB
> CRC a4e38b86
> Kernel: arch/x86/boot/bzImage is ready (#186)
> $ make kernelrelease
> scripts/kconfig/conf --silentoldconfig Kconfig 3.9.0-rc1+
> $ make kernelrelease
> 3.9.0-rc1+
>
> Happy to test the fix.
>
> Chris
>
>
>
next prev parent reply other threads:[~2013-04-01 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-09 19:38 linux-3.9.0-rc1+: Output from "make kernelrelease"contains incorrect data Chris Clayton
2013-04-01 9:28 ` Chris Clayton [this message]
2013-04-03 14:32 ` Michal Marek
2013-04-03 15:41 ` Chris Clayton
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=5159534A.1070500@googlemail.com \
--to=chris2553@googlemail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.