[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160531112251.GA5674@sophia>
Date: Tue, 31 May 2016 07:23:06 -0400
From: William Breathitt Gray <vilhelm.gray@...il.com>
To: Greg KH <gregkh@...uxfoundation.org>,
Linus Walleij <linus.walleij@...aro.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>, x86@...nel.org,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-watchdog@...r.kernel.org,
Stephen Rothwell <sfr@...b.auug.org.au>,
Guenter Roeck <linux@...ck-us.net>,
Alexandre Courbot <gnurou@...il.com>
Subject: Re: [PATCH v5 2/4] gpio: Allow PC/104 devices on X86_64
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
><vilhelm.gray@...il.com> 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 <gnurou@...il.com>
>> Cc: Linus Walleij <linus.walleij@...aro.org>
>> Reviewed-by: Guenter Roeck <linux@...ck-us.net>
>> Signed-off-by: William Breathitt Gray <vilhelm.gray@...il.com>
>
>Acked-by: Linus Walleij <linus.walleij@...aro.org>
>
>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.
Thanks,
William Breathitt Gray
Powered by blists - more mailing lists