Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp215792yba; Tue, 14 May 2019 23:24:52 -0700 (PDT) X-Google-Smtp-Source: APXvYqzuhRf3/p+DePJvpaxT77gKAcuNHWwWQYE34jHn8KwVQJscfKO5rAdyopTpkt2LYY5+3VCw X-Received: by 2002:a63:170a:: with SMTP id x10mr41217663pgl.355.1557901492258; Tue, 14 May 2019 23:24:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557901492; cv=none; d=google.com; s=arc-20160816; b=Pjuf92wX1RYqh5OceprAo/iVBWQkGYgg3/YVHnwdoryjdZlvTz1iiyOaH+fEdwBWra CC1/Z/nT23zkuFlXX+QBiu/LydNOuqDDp2yjH+E6RhpZ4FQqlN+xEzuUmreCQZUqVENh JbsRBGl65/ZLmdX4TpD9ZhxotADcR8g9utcERCKHirlwI+ud1TMdIaPgX7GTKKCtWK6W DLB8Qps1fFr5VHExsn9bLQty3PgOuE4jDnWce5HhNAc0qnER9WHcUCfuv8z/+VLp8HOl resCsWMEkQLbLvyA+DXAtz4eLpXXJfRw+cRJWIqwiCeO9aeyMN2cDMbcUSTbAqh9ePaH A9og== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:date:subject:user-agent:message-id :references:cc:in-reply-to:from:to:content-transfer-encoding :mime-version; bh=tWlUEZdbA7GRapXQoX4/KdL4yB/a0BLCwNVKXSlp0sU=; b=KZ2Tv0kdwZWpl6B9OAaZ5erlBGqDfHldZbjDKAH8e3FWITdaqDT8I7CbHk+FJ/nwo5 9eU2K6CCf4Q5btz4mbYlNS/Ipxul6Wn24zEsLOexIeboTryfIrSGWMVAVCcBoL7tfVDT d2cG0fzOrhAvvSTfAj+KKpEEAIx2x/OXUFO5zuS+zyi5k132oINw+4b+GlmBt2QDxoUG sRr1jOE7WyWa0nsjsTty5D0nLxIS3HvjY8vXXJrmwNEyJe638qKJSjCCoEiG5wZPzf6p xhJS8nFwFb7sxx1i94uoJLAMqQTCmiva9Jo33CVqw6gDJLW/xE7x4GBb5iIhgSrsyWI0 HqBw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l11si901761plb.369.2019.05.14.23.24.37; Tue, 14 May 2019 23:24:52 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725941AbfEOGXX convert rfc822-to-8bit (ORCPT + 99 others); Wed, 15 May 2019 02:23:23 -0400 Received: from mail.fireflyinternet.com ([109.228.58.192]:58195 "EHLO fireflyinternet.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725857AbfEOGXX (ORCPT ); Wed, 15 May 2019 02:23:23 -0400 X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=78.156.65.138; Received: from localhost (unverified [78.156.65.138]) by fireflyinternet.com (Firefly Internet (M1)) with ESMTP (TLS) id 16559056-1500050 for multiple; Wed, 15 May 2019 07:23:12 +0100 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8BIT To: Jani Nikula , Joonas Lahtinen , Masahiro Yamada , Rodrigo Vivi , intel-gfx@lists.freedesktop.org From: Chris Wilson In-Reply-To: <20190515043753.9853-1-yamada.masahiro@socionext.com> Cc: Dave Airlie , Sam Ravnborg , Masahiro Yamada , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, David Airlie , Daniel Vetter References: <20190515043753.9853-1-yamada.masahiro@socionext.com> Message-ID: <155790139253.21839.18331243986827594086@skylake-alporthouse-com> User-Agent: alot/0.6 Subject: Re: [PATCH] drm/i915: drop unneeded -Wall addition Date: Wed, 15 May 2019 07:23:12 +0100 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Masahiro Yamada (2019-05-15 05:37:53) > The top level Makefile adds -Wall globally: > > KBUILD_CFLAGS := -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs \ > > I see two "-Wall" added for compiling under drivers/gpu/drm/i915/. Does it matter? Is the statement in i915/Makefile not more complete for saying "-Wall -Wextra -Werror"? > Signed-off-by: Masahiro Yamada > --- > > BTW, I have a question in the comment: > > "Note the danger in using -Wall -Wextra is that when CI updates gcc we > will most likely get a sudden build breakage... Hopefully we will fix > new warnings before CI updates!" > > Enabling whatever warning options does not cause build breakage. > -Werror does. > > So, I think the correct statement is: > > "Note the danger in using -Werror is that when CI updates gcc we ... No. CI enforces -Werror and that is constant, so the uncontrolled variable, the danger, lies in using the unreliable heuristics gcc may arbitrary enable between versions. That the set of warnings causing an error may be different between CI and the developer. -Chris