From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 7AAB7A051A; Fri, 17 Jan 2020 14:25:51 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 76DAA2904; Fri, 17 Jan 2020 14:25:50 +0100 (CET) Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id C879028F3 for ; Fri, 17 Jan 2020 14:25:48 +0100 (CET) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Jan 2020 05:25:06 -0800 X-IronPort-AV: E=Sophos;i="5.70,330,1574150400"; d="scan'208";a="227188181" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.5.70]) by orsmga006-auth.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 17 Jan 2020 05:25:05 -0800 Date: Fri, 17 Jan 2020 13:25:02 +0000 From: Bruce Richardson To: Aaron Conole Cc: david.marchand@redhat.com, dev@dpdk.org Message-ID: <20200117132502.GA1714@bricha3-MOBL.ger.corp.intel.com> References: <20200117104820.71403-1-bruce.richardson@intel.com> <20200117104820.71403-2-bruce.richardson@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.1 (2019-06-15) Subject: Re: [dpdk-dev] [PATCH 2/2] doc: pass "werror" setting through to doc build X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Fri, Jan 17, 2020 at 08:16:55AM -0500, Aaron Conole wrote: > Bruce Richardson writes: > > > When werror is set for the build, we should pass that flag through to > > sphinx so that it can flag warnings as errors too. > > > > Signed-off-by: Bruce Richardson > > --- > > I see that this actually works to generate the errors... BUT > > if we merge this it will break the build. Can you also insert a patch > to address the warning so that the series could be merged? > Ok, I didn't have any warnings in my setup, which is why I didn't see any problems. I assume that the warnings are showing up in travis? Anywhere else? /Bruce