From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jon Loeliger Subject: Re: [PATCH v2] dtc: Remove spurious output on stderr Date: Sat, 14 Apr 2012 09:04:58 -0500 Message-ID: References: <1334170516-23473-1-git-send-email-sjg@chromium.org> <1334187146-8384-1-git-send-email-sjg@chromium.org> <20120411233459.GC8024@truffala.fritz.box> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-reply-to: <20120411233459.GC8024-MK4v0fQdeXQXU02nzanrWNbf9cGiqdzd@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org Sender: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org To: David Gibson Cc: Devicetree Discuss List-Id: devicetree@vger.kernel.org > On Wed, Apr 11, 2012 at 04:32:26PM -0700, Simon Glass wrote: > > Outputing to stderr is best avoided unless there is an error or warning to > > display. At present dtc always displays the name of the file it is compiling > > and the input/output formats. For example: > > > > DTC: dts->dts on file "-" > > > > This can cause problems in some build systems. For example, U-Boot shows > > build errors for any boards which use dtc at present. It is typically the > > only message output during such a build. The C compiler does not output > > anything in general. The current dtc behaviour makes it difficult to > > provide a silent build in the normal case where nothing went wrong. > > > > Remove the message entirely. > > > > Signed-off-by: Simon Glass > > Acked-by: David Gibson Applied. Thanks, jdl