From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Sun, 20 Sep 2015 23:04:22 +0200 Subject: [Buildroot] [PATCH] Makefile: Remove KBUILD_VERBOSE and quiet In-Reply-To: <55FF1A8A.5030507@openmailbox.org> References: <1441658846-5786-1-git-send-email-cedric.marie@openmailbox.org> <20150920151157.7dc9b021@free-electrons.com> <55FF1A8A.5030507@openmailbox.org> Message-ID: <20150920230422.4838bded@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello, On Sun, 20 Sep 2015 22:43:54 +0200, C?dric Marie wrote: > Le 20/09/2015 15:11, Thomas Petazzoni a ?crit : > > Following the discussion you had with Arnout, and your own report that > > this patch was breaking things in the Busybox and Linux kernel build, I > > marked this patch as "Changes Requested" in patchwork. > > > > Will you work on a new iteration of this patch? > > Yes, I've started to work on a new iteration. It is working fine with > CMake, autotools, and Kbuild packages (I keep on exporting > KBUILD_VERBOSE as suggested by Arnout). > > I still have to: > > - modify qt.mk because it currently enables verbose mode if VERBOSE is > defined and not empty, but my modification implies that VERBOSE may be > equal to 0, and it should not enable verbose mode in that case!... > - check that no other package .mk file is using VERBOSE variable. > - write clear comments and commit message. Excellent, thanks! > Sorry for the delay, but I've got only very occasional free time to > spend on it. No problem at all. I just e-mailed you to let you know that your patch has been marked "Changes Requested": it means that it is no longer visible in the list of pending patches to be considered by the maintainers. So when this is done, it is up to the submitter to come back at some point with a new iteration of the patch, otherwise the topic will simply be forgotten by the maintainers. This is why I generally send a notification e-mail when changing a patch to "Changes Requested". There is obviously no problem if the new iteration only comes in several weeks or even months. Thanks again, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com