From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755004AbcEaPZp (ORCPT ); Tue, 31 May 2016 11:25:45 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:44536 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751078AbcEaPZn (ORCPT ); Tue, 31 May 2016 11:25:43 -0400 Date: Tue, 31 May 2016 08:25:41 -0700 From: Greg KH To: William Breathitt Gray Cc: Linus Walleij , Andrew Morton , x86@kernel.org, "linux-next@vger.kernel.org" , "linux-gpio@vger.kernel.org" , "linux-iio@vger.kernel.org" , "linux-kernel@vger.kernel.org" , linux-watchdog@vger.kernel.org, Stephen Rothwell , Guenter Roeck , Alexandre Courbot Subject: Re: [PATCH v5 2/4] gpio: Allow PC/104 devices on X86_64 Message-ID: <20160531152541.GB13304@kroah.com> References: <61880bededb77bbc3ea3422e48ce717d2a2ff489.1464380034.git.vilhelm.gray@gmail.com> <20160531112251.GA5674@sophia> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160531112251.GA5674@sophia> User-Agent: Mutt/1.6.1 (2016-04-27) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 31, 2016 at 07:23:06AM -0400, William Breathitt Gray wrote: > On Tue, May 31, 2016 at 10:41:49AM +0200, Linus Walleij wrote: > >On Sat, May 28, 2016 at 12:08 AM, William Breathitt Gray > > wrote: > > > >> With the introduction of the ISA_BUS_API Kconfig option, ISA-style > >> drivers may be built for X86_64 architectures. This patch changes the > >> ISA Kconfig option dependency of the PC/104 drivers to ISA_BUS_API, thus > >> allowing them to build for X86_64 as they are expected to. > >> > >> Cc: Alexandre Courbot > >> Cc: Linus Walleij > >> Reviewed-by: Guenter Roeck > >> Signed-off-by: William Breathitt Gray > > > >Acked-by: Linus Walleij > > > >Or should I apply this directly to the GPIO tree? > > > >Yours, > >Linus Walleij > > Greg K-H, > > Would you be able to pick up this entire patchset via driver-core; I > figure that tree is the most appropriate to receive any core ISA bus > driver changes (unless you see a more fitting path to take). > > If possible, I'd like this patchset to find its way into one of the > coming release candidates in order to resolve the regression mentioned > in the cover letter: as of 4.7-rc1, the drivers which switched to > utilize the ISA bus driver are now restricted to X86_32 despite being > allowed in X86_64 in the 4.6 release. Yes, I can take this through the driver core tree as that's where the original series came from... thanks, greg k-h