Received: by 2002:ac0:a679:0:0:0:0:0 with SMTP id p54csp573886imp; Wed, 20 Feb 2019 05:25:32 -0800 (PST) X-Google-Smtp-Source: AHgI3IbFtnNqdKlAtQUdF35kbc0GS/n3MetNXBmwHC/6lSABM87gkmO/MfGYWOAWsXJUo1JSriyj X-Received: by 2002:a63:ee05:: with SMTP id e5mr6616052pgi.83.1550669132467; Wed, 20 Feb 2019 05:25:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550669132; cv=none; d=google.com; s=arc-20160816; b=xDfhLBLAOCjXRZW5s7mMMV0i7YJ3ug1cVTcmYeV8R13rIN5E4X8wf8f5/gFCt0mQME OrCmIZJ8pHCICpYzz0+9SrSfh/QeSZbJPrbMcOCpItQsWw3K9cDGn4xEZWzjNqJbD46u TVSX9hSiDnPZLmuGCIA5XCSPoPHsDZtuJ70rE2WrsZMUU6x3uvZaPSpQkbBS9rruKNpn OoOoZGaf3OhV53mGnSS3pOpehVjcLNROduMgIu7RPyuROb9RQoMmPO2wiRDaHsDXuU6n 8TwgJp+YPTavvlqXegyRLi1J4/xMauG4/Sm/V3Tzuv8KschDCHfZ5eMq8jtmLOiV83pv fzsg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :message-id:date:references:in-reply-to:subject:cc:to:from; bh=l3dNe+1GeSx5RYNnsf4dkf7oTu9rGTxsSKV6SkkOxI0=; b=Chn8u8+sPkxSfxo/x+KmHhWv5eSUQRh5Wn7KlOFb5i4mHL/kfwD6L5TBLRGUafniie C6gr25LKlEyMlET2Iwv8E/Y98eb6c+EhH/EqGIZIgPRZc5poM0s0bJNR//3svQ4p/U8y Xt7Sk8xS7jEcwgec7Eo6PivCBzF5fMxoGnIkzDQn3vw/bxOxoSqwflcEtv8mhOmnkhP1 b2dMf35liPfkC9EQ0PaBMCDN/UnWr4mIaXJbDoTVmyhA7882K2Di7lZMpEBMM1uycFW3 BjTl9PUuqFxTmvwCTbeYW5AcJLqbbzqAmI+thUNz+O/DLOeq8m6btdAt3tuxMl6X/rKQ Coag== 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 t71si4923942pgd.550.2019.02.20.05.25.16; Wed, 20 Feb 2019 05:25:32 -0800 (PST) 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 S1727551AbfBTNXP convert rfc822-to-8bit (ORCPT + 99 others); Wed, 20 Feb 2019 08:23:15 -0500 Received: from ozlabs.org ([203.11.71.1]:54231 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725869AbfBTNXP (ORCPT ); Wed, 20 Feb 2019 08:23:15 -0500 Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPSA id 444JFX0zLHz9s1B; Thu, 21 Feb 2019 00:23:12 +1100 (AEDT) From: Michael Ellerman To: Christophe Leroy , Jonathan =?utf-8?Q?Neusch?= =?utf-8?Q?=C3=A4fer?= Cc: Benjamin Herrenschmidt , Paul Mackerras , linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org Subject: Re: [PATCH v2 00/15] powerpc/32s: Use BATs/LTLBs for STRICT_KERNEL_RWX In-Reply-To: <8b072209-c845-20f5-8ff1-27ecd67b5c72@c-s.fr> References: <20190113181621.GA22334@latitude> <714e78ba-1e92-a856-3dd6-a1fb96ad3785@c-s.fr> <20190113210227.GB22334@latitude> <334b1b02-b652-499c-904e-09e6f7164b8c@c-s.fr> <20190115003353.GD22334@latitude> <87fttuz0d3.fsf@concordia.ellerman.id.au> <8b072209-c845-20f5-8ff1-27ecd67b5c72@c-s.fr> Date: Thu, 21 Feb 2019 00:23:09 +1100 Message-ID: <87ftsi7fwi.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Christophe Leroy writes: > Le 15/01/2019 à 11:22, Michael Ellerman a écrit : >> Christophe Leroy writes: >>> Le 15/01/2019 à 01:33, Jonathan Neuschäfer a écrit : >> ... >>>> >>>> - patches 7 to 11 fail to build with this error (really a warning, but >>>> arch/powerpc doesn't allow warnings by default): >>>> >>>> CC arch/powerpc/mm/ppc_mmu_32.o >>>> ../arch/powerpc/mm/ppc_mmu_32.c:133:13: error: ‘clearibat’ defined but not used [-Werror=unused-function] >>>> static void clearibat(int index) >>>> ^~~~~~~~~ >>>> ../arch/powerpc/mm/ppc_mmu_32.c:115:13: error: ‘setibat’ defined but not used [-Werror=unused-function] >>>> static void setibat(int index, unsigned long virt, phys_addr_t phys, >>>> ^~~~~~~ >>>> cc1: all warnings being treated as errors >>> >>> Argh ! I have to squash the patch bringing the new functions with the >>> one using them (patch 12). The result is a big messy patch which is more >>> difficult to review but that's life. >> >> You don't *have* to squash them. >> >> We like to preserve bisectability, but it's not a 100% hard requirement. >> >> Someone trying to bisect through those patches can always turn off >> -Werror with PPC_DISABLE_WERROR. But they probably can just skip them >> because they just add new code that's not called yet. > > Ok thanks for the note. > >> >> So I won't object if you send them as-is. > > Good to know. Anyway I think I will at least re-order so that the patch > using the new functions immediatly follows the one adding the functions. Based on that I'm expecting a v3 of this series, right? cheers