From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-kernel@vger.kernel.org, David Howells <dhowells@redhat.com>
Subject: Re: v3.16-rc4 messes up make kernelrelease with additional output
Date: Wed, 9 Jul 2014 14:20:47 +0100 [thread overview]
Message-ID: <20140709132047.GT21766@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <53BD4074.5070100@suse.cz>
On Wed, Jul 09, 2014 at 03:15:32PM +0200, Michal Marek wrote:
> On 2014-07-09 14:59, Russell King - ARM Linux wrote:
> > 3.16-rc3 and all previous versions:
> >
> > $ make ARCH=arm CROSS_COMPILE=arm-linux- O=/tmp/build/ kernelrelease
> > 3.16.0-rc3+
> > $
> >
> > 3.16-rc4:
> >
> > $ make ARCH=arm CROSS_COMPILE=arm-linux- O=/tmp/build/ kernelrelease
> > make[1]: Entering directory `/tmp/build'
> > 3.16.0-rc4+
> > $
>
> This is fixed by commit 066b7ed9 in linux-next, which I'll send to Linus
> shortly. But you should use make -s ... kernelrelease, otherwise the
> output will be polluted not only by the "Entering directory" message,
> but possibly also by a silentoldconfig run.
Since my scripts run a full build before doing that, it's very unlikely
that there would be a silentoldconfig run. The -s requirement isn't
documented in the help - should it be?
--
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2014-07-09 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 12:59 Russell King - ARM Linux
2014-07-09 13:15 ` Michal Marek
2014-07-09 13:20 ` Russell King - ARM Linux [this message]
2014-07-09 13:36 ` Michal Marek
2014-07-11 14:13 ` [PATCH] kbuild: make -s should be used with kernelrelease/kernelversion/image_name Michal Marek
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=20140709132047.GT21766@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=dhowells@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®