From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754857AbdDLVyF (ORCPT ); Wed, 12 Apr 2017 17:54:05 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:35711 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751620AbdDLVyD (ORCPT ); Wed, 12 Apr 2017 17:54:03 -0400 Date: Wed, 12 Apr 2017 23:53:59 +0200 (CEST) From: Thomas Gleixner To: Tony Luck cc: David Woodhouse , "linux-pci@vger.kernel.org" , "linux-arch@vger.kernel.org" , Linux Kernel Mailing List Subject: Re: [PATCH v2 25/27] ia64: Use generic pci_mmap_resource_range() In-Reply-To: Message-ID: References: <109e9ddbde4334d0da34f331797236309d789353.1491999859.git.dwmw2@infradead.org> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 12 Apr 2017, Tony Luck wrote: > On Wed, Apr 12, 2017 at 5:26 AM, David Woodhouse wrote: > > From: David Woodhouse > > > > Now that we eliminated the different behaviour in separately-reviewable > > commits, we can switch IA64 to the generic implementation. > > > > Signed-off-by: David Woodhouse > > Well it builds and boots on my last remaining ia64 machine. Does that mean ia64 reached the 'NCR Voyager' stage and can be scheduled for removal? Thanks, tglx