From: Michal Marek <mmarek@suse.cz>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Masahiro Yamada <yamada.m@jp.panasonic.com>,
Peter Foley <pefoley2@pefoley.com>,
linux-kbuild@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] kbuild: Fix output of make kernelrelease
Date: Thu, 23 Oct 2014 10:50:37 +0200 [thread overview]
Message-ID: <5448C15D.9060505@suse.cz> (raw)
In-Reply-To: <20141022163507.6e2162d1@gandalf.local.home>
On 2014-10-22 22:35, Steven Rostedt wrote:
> On Wed, 22 Oct 2014 21:44:08 +0200
> Michal Marek <mmarek@suse.cz> wrote:
>
>> Dne 22.10.2014 v 16:19 Steven Rostedt napsal(a):
>>>
>>> Commit 7ff525712acf "kbuild: fake the "Entering directory ..." message
>>> more simply" changed the output of "make kernelrelease" such that the
>>> kernel release version was not the last line printed. This broke various
>>> tools that would find the kernel release with "make kernelrelease | tail -1".
>>
>> The cleaner and recommended (see recent make help) way is to use make -s:
>>
>> $ make O=build -s kernelrelease
>> 3.18.0-rc1+
>
> Hmm, I see the help index was recently updated to include that.
>
> Does this work with older kernels too? That's very important.
Yes. Except for a few bugs in the history, make -s has always been silent.
Michal
next prev parent reply other threads:[~2014-10-23 8:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 14:19 [PATCH] kbuild: Fix output of make kernelrelease Steven Rostedt
2014-10-22 19:44 ` Michal Marek
2014-10-22 19:44 ` Michal Marek
2014-10-22 20:35 ` Steven Rostedt
2014-10-23 8:50 ` Michal Marek [this message]
2014-10-23 1:11 ` Steven Rostedt
2014-10-23 8:57 ` Michal Marek
2014-10-23 10:51 ` Steven Rostedt
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=5448C15D.9060505@suse.cz \
--to=mmarek@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pefoley2@pefoley.com \
--cc=rostedt@goodmis.org \
--cc=yamada.m@jp.panasonic.com \
/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.