linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: William Breathitt Gray <vilhelm.gray@gmail.com>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
	Linus Walleij <linus.walleij@linaro.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	x86@kernel.org,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-watchdog@vger.kernel.org,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Guenter Roeck <linux@roeck-us.net>,
	Alexandre Courbot <gnurou@gmail.com>,
	sasha.levin@oracle.com, xiaolong.ye@intel.com
Subject: Re: [PATCH v5 2/4] gpio: Allow PC/104 devices on X86_64
Date: Fri, 17 Jun 2016 20:47:31 -0700	[thread overview]
Message-ID: <20160618034731.GA1815@kroah.com> (raw)
In-Reply-To: <20160618033812.GA20596@sophia>

On Fri, Jun 17, 2016 at 11:39:04PM -0400, William Breathitt Gray wrote:
> On Fri, Jun 17, 2016 at 08:18:10PM -0700, Greg KH wrote:
> >On Fri, Jun 17, 2016 at 10:49:59PM -0400, William Breathitt Gray wrote:
> >> The PC/104 drivers were changed to utilize the ISA bus driver as part of
> >> the original patchset which attempted to decouple the X86_32 dependency
> >> from the ISA Kconfig option; these drivers were updated with the
> >> intention of building on X86_64 in addition to X86_32.
> >> 
> >> However, the respective patches were merged without the decoupling
> >> changes (since decoupling was the wrong approach), resulting in an
> >> unintentional regression: the PC/104 drivers are now restricted to
> >> X86_32 due to the ISA Kconfig option dependency, while they were capable
> >> of building for X86_64 in previous kernel versions.
> >> 
> >> This patchset should fix this regression by introducing the ISA_BUS_API
> >> Kconfig option, and the respective Kconfig dependency changes for the
> >> drivers, in order to allow them to build for both X86_64 and X86_32 as
> >> originally capable.
> >
> >Ah, ok, that makes more sense, thanks.  I'll go queue these up now.
> >
> >greg k-h
> 
> Greg K-H,
> 
> Please also consider picking up the following two patches which fix bugs
> discovered during the ISA bus driver utilization conversion:
> 
>   1. https://patchwork.kernel.org/patch/9046831/
>   2. https://patchwork.kernel.org/patch/9074641/
> 
> The second patch in particular fixes a kernel BUG which prevents some
> drivers that call isa_register_driver from being built-in. This was
> first reported by Sasha Levin (https://lkml.org/lkml/2016/5/11/719), and
> the patch was later tested by Ye Xiaolong
> (https://lkml.org/lkml/2016/5/31/164).

Now queued up, thanks for the prompt, they were still setting in my
queue.

greg k-h

  reply	other threads:[~2016-06-18  3:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-27 22:08 [PATCH v5 0/4] Allow ISA-style drivers on modern systems William Breathitt Gray
2016-05-27 22:08 ` [PATCH v5 1/4] isa: " William Breathitt Gray
2016-05-28 19:35   ` Linus Torvalds
2016-05-27 22:08 ` [PATCH v5 2/4] gpio: Allow PC/104 devices on X86_64 William Breathitt Gray
2016-05-31  8:41   ` Linus Walleij
2016-05-31 11:23     ` William Breathitt Gray
2016-05-31 15:25       ` Greg KH
2016-06-17 10:47         ` Thorsten Leemhuis
2016-06-18  2:36           ` Greg KH
2016-06-18  2:49             ` William Breathitt Gray
2016-06-18  3:18               ` Greg KH
2016-06-18  3:39                 ` William Breathitt Gray
2016-06-18  3:47                   ` Greg KH [this message]
2016-05-27 22:09 ` [PATCH v5 3/4] iio: stx104: Allow build for X86_64 William Breathitt Gray
2016-05-28 17:15   ` Jonathan Cameron
2016-05-27 22:09 ` [PATCH v5 4/4] watchdog: ebc-c384_wdt: " William Breathitt Gray

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160618034731.GA1815@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=gnurou@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=regressions@leemhuis.info \
    --cc=sasha.levin@oracle.com \
    --cc=sfr@canb.auug.org.au \
    --cc=vilhelm.gray@gmail.com \
    --cc=x86@kernel.org \
    --cc=xiaolong.ye@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).