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=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS 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 58B83C43381 for ; Tue, 5 Mar 2019 07:50:57 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 305502082C for ; Tue, 5 Mar 2019 07:50:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727257AbfCEHuz (ORCPT ); Tue, 5 Mar 2019 02:50:55 -0500 Received: from mail-ua1-f65.google.com ([209.85.222.65]:44862 "EHLO mail-ua1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727042AbfCEHuz (ORCPT ); Tue, 5 Mar 2019 02:50:55 -0500 Received: by mail-ua1-f65.google.com with SMTP id r21so6896788uan.11 for ; Mon, 04 Mar 2019 23:50:54 -0800 (PST) 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=FJQy2eZmxa2kZTjrpayF6beH9mz6o6lejKOYF66JVEM=; b=ZEBFUvhxwe6UqruplYyejIlY2fg0YMhencGCVfwVqnVFlg8xWrP8KJaNy00VVNObTq 6PWmNx+3YHIn7291fiIRcIVDuGnZxiZM7KRMVGh63DoyfPcwpir45CfdXgz9UK29HT5i SqvqSPxjaOSkcbCWchq6vpWUKtrYDxXoOUMWviG7QKZQ+a+aJmZqMb4Y4+wW7HlCZMlR mAngMR3CDjxMYjubVgVor/cRTYHyg8rd76HjzFbKwhG+50Pcwk4zgQ3W4LkF5C906a2f 0JfL/NtPWWahZAP8frODrmetQqHeGzsNAhzq6nyFdhne21SVgy2bE0xoVIS30fCQYtBb Js1g== X-Gm-Message-State: APjAAAVg6iZToVG6qjbLTsQkHJ0fQRrCshJ1PqAIdJxg7EVo+gIP7BLc 6IYzxfaZHrj/Bb7Y4Fs6ZkLtiBK0ezTmf7nc2Ks= X-Google-Smtp-Source: APXvYqyh2va6B2XakHivRwk9rKnCts/W9zwI154TdDOqtxv5U5F4TJ/aHNN8G1xlkkr4G4fHgxBXmDZuR6zXbD1ky8Y= X-Received: by 2002:a9f:30dc:: with SMTP id k28mr532005uab.75.1551772254083; Mon, 04 Mar 2019 23:50:54 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Geert Uytterhoeven Date: Tue, 5 Mar 2019 08:50:42 +0100 Message-ID: Subject: Re: [PATCH v4 00/14] m68k: Drop arch_gettimeoffset and adopt clocksource API To: Finn Thain Cc: Andreas Schwab , Arnd Bergmann , Stephen N Chivers , Thomas Gleixner , Kars de Jong , Daniel Lezcano , Michael Schmitz , John Stultz , Linus Walleij , linux-m68k , Linux Kernel Mailing List 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 Hi Finn, On Tue, Mar 5, 2019 at 7:13 AM Finn Thain wrote: > On Sat, 1 Dec 2018, Finn Thain wrote: > > This series removes "select ARCH_USES_GETTIMEOFFSET" from arch/m68k > > and converts users of arch_gettimeoffset to the clocksource API. > > Various bugs are fixed along the way. > > Are there any plans to merge this series, Geert? Has this been tested on all/most platforms? Or do you think is it safe to apply regardless? Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds