Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753040AbcKOQbD (ORCPT ); Tue, 15 Nov 2016 11:31:03 -0500 Received: from mail-yw0-f196.google.com ([209.85.161.196]:34538 "EHLO mail-yw0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751359AbcKOQbB (ORCPT ); Tue, 15 Nov 2016 11:31:01 -0500 MIME-Version: 1.0 In-Reply-To: References: From: Linus Torvalds Date: Tue, 15 Nov 2016 08:30:59 -0800 X-Google-Sender-Auth: oYVDj-whZBz1NrBid01JnJkszUQ Message-ID: Subject: Re: [GIT PULL] fbdev fixes for 4.9 To: Tomi Valkeinen Cc: linux-fbdev , "linux-kernel@vger.kernel.org" , Mathieu Malaterre Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 603 Lines: 16 On Tue, Nov 15, 2016 at 3:40 AM, Tomi Valkeinen wrote: > > I did test compile, and I would have noticed errors but I missed the warnings > (I blame the flu...). I need to improve my testing methods, but I couldn't find > a way to add -Werror to kernel builds. I guess I should just always capture the > warnings and errors to a file, and check that after the build. > > How do you test build? I basically do just an allmodconfig build, but I do it with make -j16 > ../make-output so that any warnings are very obvious (because stdout goes elsewhere). Linus