From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S935456AbdEWHEy (ORCPT <rfc822;w@1wt.eu>);
        Tue, 23 May 2017 03:04:54 -0400
Received: from verein.lst.de ([213.95.11.211]:52243 "EHLO newverein.lst.de"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S933280AbdEWHEw (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 23 May 2017 03:04:52 -0400
Date: Tue, 23 May 2017 09:04:50 +0200
From: Christoph Hellwig <hch@lst.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Christoph Hellwig <hch@lst.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel: mark all struct k_clock instances const
Message-ID: <20170523070450.GA17926@lst.de>
References: <20170515203213.25080-1-hch@lst.de> <alpine.DEB.2.20.1705222319350.2407@nanos> <20170523044851.GA15761@lst.de> <alpine.DEB.2.20.1705230900150.2740@nanos>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.20.1705230900150.2740@nanos>
User-Agent: Mutt/1.5.17 (2007-11-01)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, May 23, 2017 at 09:01:14AM +0200, Thomas Gleixner wrote:
> > We can require the driver to be built into the kernel, which seems pretty
> > reasonable for a timer.  It's only selectable on IA64 anyway.
> 
> That still requires that we "register" the clock as it's SN2 specific and
> we don't want to end up with a non initialized clock ....

I'd much rather have a call to mmtimer_init from the core clock
code than having to conditionally export the array..

But maybe we can actually drop the mmtimer now - IA64-based Altix
systems haven't been built for a while and anyone requiring its
special clock will run a distro of sorts anyway.