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=-4.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED 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 5DA3AC46470 for ; Wed, 22 May 2019 21:16:23 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0BACE21773 for ; Wed, 22 May 2019 21:16:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730195AbfEVVQW (ORCPT ); Wed, 22 May 2019 17:16:22 -0400 Received: from mail-qt1-f193.google.com ([209.85.160.193]:37203 "EHLO mail-qt1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729720AbfEVVQW (ORCPT ); Wed, 22 May 2019 17:16:22 -0400 Received: by mail-qt1-f193.google.com with SMTP id o7so4248837qtp.4; Wed, 22 May 2019 14:16:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IRDeg6juu9TInpGEUEsh12JdfkX4fbWASfCdn5kwEwo=; b=l/GM5KjopFjgbnIKVrkQBcZQ7sudlrvhjbQ4BC0yhixsuYYj3KZxqvREtYjHssMFvV c9zBIzzPTmU9Oz8V63hsEdABFGmxdYY6/QMb5DwdhcqEPBleWafiT7m32391zpKJHEPa wKKZ7BxqWO6+nmPPBpKokLXZa6ld4hjH4mb1vajY0vpWVqp8wWcQtrc8oqIsLWurnEsk DER9cebLKx3usmC4h0SxTAPh0gC4XmP9e/I4jN1qh3vUCYydiyoipWLzYQ9yRLQjgR4C EeX0DOLeeowoI/QsIuMzenvb+CbSPugImu8Uj9T50geezggMW3IZg/FMgldGoKIhT074 RikQ== X-Gm-Message-State: APjAAAVvynSpr4/Desi1FEh3TfHd1iHdn+snK9mqP25eD4R7eDDoqfT1 Jk245gKmFIksvba66Qd8tqwQWmOs0TxkkfikrJI= X-Google-Smtp-Source: APXvYqxRHIuj8C7LagjHY5o0vw8tutrohkTAg2q5dHo9HC3r8+VsVxO6QVsI0OWyf9koBryzkBEG0/AKdXcmD+aAbnk= X-Received: by 2002:ac8:3319:: with SMTP id t25mr76253431qta.204.1558559781276; Wed, 22 May 2019 14:16:21 -0700 (PDT) MIME-Version: 1.0 References: <20190522132250.26499-1-mark.rutland@arm.com> <20190522132250.26499-4-mark.rutland@arm.com> In-Reply-To: <20190522132250.26499-4-mark.rutland@arm.com> From: Arnd Bergmann Date: Wed, 22 May 2019 23:16:04 +0200 Message-ID: Subject: Re: [PATCH 03/18] locking/atomic: generic: use s64 for atomic64 To: Mark Rutland Cc: Linux Kernel Mailing List , Peter Zijlstra , Will Deacon , Albert Ou , Borislav Petkov , Catalin Marinas , David Miller , Fenghua Yu , Heiko Carstens , Herbert Xu , Ivan Kokshaysky , James Hogan , Russell King - ARM Linux , Matt Turner , Ingo Molnar , Michael Ellerman , Palmer Dabbelt , Paul Burton , Paul Mackerras , Ralf Baechle , Richard Henderson , "# 3.4.x" , Thomas Gleixner , Tony Luck , Vineet Gupta Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 22, 2019 at 3:23 PM Mark Rutland wrote: > > As a step towards making the atomic64 API use consistent types treewide, > let's have the generic atomic64 implementation use s64 as the underlying > type for atomic64_t, rather than long long, matching the generated > headers. > > Otherwise, there should be no functional change as a result of this > patch. > > Signed-off-by: Mark Rutland > Cc: Peter Zijlstra > Cc: Will Deacon Acked-by: Arnd Bergmann