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,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 92BCDC43381 for ; Mon, 25 Mar 2019 09:25:50 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6BEBF2085A for ; Mon, 25 Mar 2019 09:25:50 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730285AbfCYJZt (ORCPT ); Mon, 25 Mar 2019 05:25:49 -0400 Received: from mail-ua1-f67.google.com ([209.85.222.67]:38200 "EHLO mail-ua1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730147AbfCYJZs (ORCPT ); Mon, 25 Mar 2019 05:25:48 -0400 Received: by mail-ua1-f67.google.com with SMTP id d4so2735755uap.5 for ; Mon, 25 Mar 2019 02:25:48 -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=YyXgsi7Hmr4fSWEM1/z6vwIkuMzubjld/R4CuByIhuo=; b=C72Srl15sQKD2sAfjw8LlZyhhFH5SwvNbCyhPAOTALnFcZdSaCWA6C906sKRwvdakp 5C5zCawLqN8LoSORQJQyeS9xldiBvBMCSx6XsqsaEMWejbdDJqWNLfPMTZKvL9M/9gWR sghzuUq8X6txHCzgNJfKbnjen/BYA37ZkOffof4RlnMSqbEwZhy5xvTLzAfgZbd9rRHs jHoRmxV5Pa3c/rUOoT+EcG4+7SsKY4SKWH1Xny+5sy1Ln/ksFbOF9NdH9ueFGyngY522 kG+QhpW43mDe5XqSbg94Aql5yjueg0pTt2ZM69fcMvPYqDAlP8pyjg4xCvm0vTQYGG7+ 6S7A== X-Gm-Message-State: APjAAAUyR7Zh8Bsi+JncIQ6POunNm38toByZ4629lXOxtA6Ay7QsGMW9 Dmd3mBemFsidHckznmrnN5gmY7p0OqJtxjmJX6s= X-Google-Smtp-Source: APXvYqwSswZxYDvJ7jKlJvXdykHaAYG5nqWq2RuDufDuUtO4DhUL0Xt5Ej2am2q5BX+wvZ6Z5HQRqmjkba2Fpys7THI= X-Received: by 2002:ab0:6419:: with SMTP id x25mr8914472uao.86.1553505947478; Mon, 25 Mar 2019 02:25:47 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Geert Uytterhoeven Date: Mon, 25 Mar 2019 10:25:36 +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 10:55 AM Finn Thain wrote: > On Tue, 5 Mar 2019, Geert Uytterhoeven wrote: > > 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? > > > > The amiga, atari and mac patches have been tested. > > The apollo, q40, sun3 and sun3x patches are safe though untested, AFAIK. I > confirmed that, in qemu at least, the default jiffies clocksource will > work, and the patch is trivial. > > That leaves bvme6000, hp300, mvme147 and mvme16x. Those have not been > tested. Here are some options for those platforms: > > 1) Apply the patches untested (gaining new clocksources and some API > modernization for m68k, while fixing old bugs and potentially introducing > new bugs). Thank you, applied and queued for v5.2. 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