From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A538AC3279B for ; Wed, 4 Jul 2018 15:28:11 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 686AC2242C for ; Wed, 4 Jul 2018 15:28:11 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 686AC2242C Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=arm.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753165AbeGDP2J (ORCPT ); Wed, 4 Jul 2018 11:28:09 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:39354 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753131AbeGDP2H (ORCPT ); Wed, 4 Jul 2018 11:28:07 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 90AA918A; Wed, 4 Jul 2018 08:28:07 -0700 (PDT) Received: from edgewater-inn.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id 621DA3F5AD; Wed, 4 Jul 2018 08:28:07 -0700 (PDT) Received: by edgewater-inn.cambridge.arm.com (Postfix, from userid 1000) id 5A2861AE189D; Wed, 4 Jul 2018 16:28:47 +0100 (BST) Date: Wed, 4 Jul 2018 16:28:47 +0100 From: Will Deacon To: Mark Rutland Cc: linux-kernel@vger.kernel.org, peterz@infradead.org, boqun.feng@gmail.com Subject: Re: [PATCHv2 08/11] atomics: switch to generated fallbacks Message-ID: <20180704152846.GL4828@arm.com> References: <20180625105952.3756-1-mark.rutland@arm.com> <20180625105952.3756-9-mark.rutland@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180625105952.3756-9-mark.rutland@arm.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 25, 2018 at 11:59:49AM +0100, Mark Rutland wrote: > As a step to ensuring the atomic* APIs are consistent, switch to fallbacks > generated by gen-atomic-fallback.sh. > > These are checked in rather than generated with Kbuild, since: > > * This allows inspection of the atomics with git grep and ctags on a > pristine tree, which Linus strongly prefers being able to do. > > * The fallbacks are not expected to change very often, and are not > affected by machine details or configuration options, so regenerating > them for *every* build is somewhat wasteful. > > * These are included by files required *very* early in the build process > (e.g. for generating bounds.h), and we'd rather not complicate the > top-level Kbuild file. Would it be worth checking that the generated output from the script doesn't differ from the file in tree at some point during the build, and issuing a warning if they do? Will