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.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no 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 A3D74C55178 for ; Sun, 1 Nov 2020 09:53:53 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6D4CF20853 for ; Sun, 1 Nov 2020 09:53:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1604224433; bh=HyGP8CyzoSVv4MCtKqC0pz2ILBHefcA84mBlIyrXGQY=; h=References:In-Reply-To:From:Date:Subject:To:Cc:List-ID:From; b=14GHiFY8IK/YiV0rATo2wQIe20Gi/pxO6vuS6CzwntHyDc2+BW5cyq0WFP1ETby7t xtdkDBptr+1zOXwyeKJmdEdG230jJaGfdTPLyXSZeuiv2pVsLxluHcjgVyxHmP38yC Vok408Xp+RMjjHjvB41YBtaO8r8yCRUz4rdixF3U= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726152AbgKAJxv (ORCPT ); Sun, 1 Nov 2020 04:53:51 -0500 Received: from mail.kernel.org ([198.145.29.99]:41758 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726118AbgKAJxu (ORCPT ); Sun, 1 Nov 2020 04:53:50 -0500 Received: from mail-qt1-f178.google.com (mail-qt1-f178.google.com [209.85.160.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 0AF4C2224F; Sun, 1 Nov 2020 09:53:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1604224430; bh=HyGP8CyzoSVv4MCtKqC0pz2ILBHefcA84mBlIyrXGQY=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=OMq+e5xfRYGK+MPaFvjA5XQ1EtstRGebvmfrK3+vfb+arDfLov6n8hi7lEhvA8JZE z40cxD0hw5blLj6L2UKYdnzi/5gtxIYmBfUclxCvOu7zyF6h6jCeq4xX2W5yTZ2wGD slN22E9LD6wvSE4f/dRWU2vJNnSXKl/+kfGMYbls= Received: by mail-qt1-f178.google.com with SMTP id j62so7328369qtd.0; Sun, 01 Nov 2020 01:53:50 -0800 (PST) X-Gm-Message-State: AOAM5317nET48x+nl/anPhsPgD35Tm3tPMqLzxGI6ic3QT5r6MSHLApG jWxlmLOLWyDqbxrrQ/3ba6fY0+eY/+0LM11vFeY= X-Google-Smtp-Source: ABdhPJysxelGXEjcD+tK3eXvueDK0E9An/zQqCvczumw3UuNNLcEVvMETDYrwUeexoouBWqMdjrPCeGJVcKk4WzZomA= X-Received: by 2002:ac8:7955:: with SMTP id r21mr9418714qtt.204.1604224429108; Sun, 01 Nov 2020 01:53:49 -0800 (PST) MIME-Version: 1.0 References: <20201030151758.1241164-1-arnd@kernel.org> In-Reply-To: From: Arnd Bergmann Date: Sun, 1 Nov 2020 10:53:33 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 00/15] timers: clean up ARCH_GETTIMEOFFSET, LEGACY_TIMER_TICK To: Finn Thain Cc: "linux-kernel@vger.kernel.org" , Thomas Gleixner , Arnd Bergmann , Russell King , Tony Luck , Fenghua Yu , Greg Ungerer , Philip Blundell , Joshua Thompson , Sam Creasey , "James E.J. Bottomley" , Helge Deller , Daniel Lezcano , John Stultz , Stephen Boyd , Linus Walleij , linux-ia64@vger.kernel.org, Parisc List , linux-m68k , Linux ARM Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-parisc@vger.kernel.org On Sun, Nov 1, 2020 at 4:47 AM Finn Thain wrote: > > On Fri, 30 Oct 2020, Arnd Bergmann wrote: > > > CONFIG_ARCH_GETTIMEOFFSET has been gradually phased out from all > > platforms, with only ARM EBSA110 recently. As this has no more known > > users, the first three patches remove EBSA110 along with one platform > > specific driver and the ARCH_GETTIMEOFFSET infrastructure. > > > > The CONFIG_ARCH_GETTIMEOFFSET patches weren't part of v1. Is there some > kind of dependency here? There is technically a dependency, though nobody would notice in practice: removing the ARM timer tick function in patch 6 would break the ebsa110 platform if we didn't first remove it in patch 1. Changing ebsa110 to use legacy_timer_tick in turn would introduce a conflict against the removal patch. Neither of those is particularly harmful as there are no users of the affected ebsa110 code, but keeping the two series together avoids getting complaints from the build bots. Arnd