From: Michal Marek <mmarek@suse.cz>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
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, 09 Jul 2014 15:36:47 +0200 [thread overview]
Message-ID: <53BD456F.5040209@suse.cz> (raw)
In-Reply-To: <20140709132047.GT21766@n2100.arm.linux.org.uk>
On 2014-07-09 15:20, Russell King - ARM Linux wrote:
> 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?
It should probably be.
Michal
next prev parent reply other threads:[~2014-07-09 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 12:59 v3.16-rc4 messes up make kernelrelease with additional output Russell King - ARM Linux
2014-07-09 13:15 ` Michal Marek
2014-07-09 13:20 ` Russell King - ARM Linux
2014-07-09 13:36 ` Michal Marek [this message]
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=53BD456F.5040209@suse.cz \
--to=mmarek@suse.cz \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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