From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S969009AbdEXAgY (ORCPT ); Tue, 23 May 2017 20:36:24 -0400 Received: from g9t1613g.houston.hpe.com ([15.241.32.99]:50113 "EHLO g9t1613g.houston.hpe.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S968988AbdEXAgQ (ORCPT ); Tue, 23 May 2017 20:36:16 -0400 Date: Tue, 23 May 2017 19:36:01 -0500 From: Dimitri Sivanich To: Thomas Gleixner Cc: Christoph Hellwig , Dimitri Sivanich , Nate Zimmer , Russ Anderson , LKML , Mike Travis Subject: Re: status of the Altix mmtimer driver Message-ID: <20170524003601.GB23931@hpe.com> References: <20170523070805.GB17926@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Since this is SN2 specific, this can be removed. On Tue, May 23, 2017 at 05:27:16PM +0200, Thomas Gleixner wrote: > On Tue, 23 May 2017, Christoph Hellwig wrote: > > Cc: + Mike > > > 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. > >