public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 2/2] kconfig: Do not print status messages in make -s mode
Date: Thu, 09 Apr 2015 14:58:29 +0200	[thread overview]
Message-ID: <55267775.3080407@suse.cz> (raw)
In-Reply-To: <1428583676.14000.50.camel@x220>

On 2015-04-09 14:47, Paul Bolle wrote:
> On Wed, 2015-04-08 at 13:42 +0200, Michal Marek wrote:
>> Add an -s option to the conf, mconf, qconf and gconf frontends and pass
>> it when make -s is used.
> 
> Basically this suppresses everything except warning and errors,
> correct? 

Yes, that's what make -s is expected to do.


> I don't actually use nconf. Is it already silent?

Yes.


> (I had to look up $(kecho). I found:
>     ###
>     # Easy method for doing a status message
>            kecho := :
>      quiet_kecho := echo
>     silent_kecho := :
>     kecho := $($(quiet)kecho)
> 
> I'm not fluent in Makefilese. What does it provide beyond @echo?)

See Documentation/kbuild/makefiles.txt.


> The patch adds this :
>     conf_set_message_callback(NULL);
> 
> for conf, gconf, and qconf. That won't work for mconf?

Have you tried looking at the mconf code? It sets a message callback to
display ncurses dialogs.

Michal

  reply	other threads:[~2015-04-09 12:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 11:42 [PATCH 1/2] kconfig: Simplify Makefile Michal Marek
2015-04-08 11:42 ` [PATCH 2/2] kconfig: Do not print status messages in make -s mode Michal Marek
2015-04-09 12:47   ` Paul Bolle
2015-04-09 12:58     ` Michal Marek [this message]
2015-04-09 14:58       ` Paul Bolle
2015-04-09 15:46         ` Michal Marek
2015-04-09  1:43 ` [PATCH 1/2] kconfig: Simplify Makefile Masahiro Yamada

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=55267775.3080407@suse.cz \
    --to=mmarek@suse.cz \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    /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