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 S965992AbdEWHIK (ORCPT <rfc822;w@1wt.eu>);
        Tue, 23 May 2017 03:08:10 -0400
Received: from verein.lst.de ([213.95.11.211]:52258 "EHLO newverein.lst.de"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S965061AbdEWHIH (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 23 May 2017 03:08:07 -0400
Date: Tue, 23 May 2017 09:08:05 +0200
From: Christoph Hellwig <hch@lst.de>
To: Dimitri Sivanich <sivanich@sgi.com>, Nate Zimmer <nzimmer@sgi.com>,
        Russ Anderson <rja@sgi.com>
Cc: Thomas Gleixner <tglx@linutronix.de>, linux-kernel@vger.kernel.org
Subject: sttus of the Altix mmtimer driver
Message-ID: <20170523070805.GB17926@lst.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
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

Hi folks,

what's the status of the SGI support for the IA64 SN2-specific
altic mmtimer (drivers/char/mmtimer.c)?  It's the only driver that
register a k_lock outside the core kernel, so if we could get rid of
it because the remaining IA64 user are all on somewhat old distros
anyway it would make our life a whole lot easier.