public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation•org>
To: William Breathitt Gray <vilhelm.gray@gmail•com>
Cc: 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>
Subject: Re: [PATCH v5 2/4] gpio: Allow PC/104 devices on X86_64
Date: Tue, 31 May 2016 08:25:41 -0700	[thread overview]
Message-ID: <20160531152541.GB13304@kroah.com> (raw)
In-Reply-To: <20160531112251.GA5674@sophia>

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
> ><vilhelm.gray@gmail•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@gmail•com>
> >> Cc: Linus Walleij <linus.walleij@linaro•org>
> >> Reviewed-by: Guenter Roeck <linux@roeck-us•net>
> >> Signed-off-by: William Breathitt Gray <vilhelm.gray@gmail•com>
> >
> >Acked-by: Linus Walleij <linus.walleij@linaro•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.

Yes, I can take this through the driver core tree as that's where the
original series came from...

thanks,

greg k-h

  reply	other threads:[~2016-05-31 15:25 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
     [not found]   ` <61880bededb77bbc3ea3422e48ce717d2a2ff489.1464380034.git.vilhelm.gray-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-05-31  8:41     ` Linus Walleij
2016-05-31 11:23       ` William Breathitt Gray
2016-05-31 15:25         ` Greg KH [this message]
2016-06-17 10:47           ` Thorsten Leemhuis
     [not found]             ` <057d8c0b-074c-609a-35da-5a01f07b6d31-rCxcAJFjeRkk+I/owrrOrA@public.gmane.org>
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
     [not found] ` <cover.1464380034.git.vilhelm.gray-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
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=20160531152541.GB13304@kroah.com \
    --to=gregkh@linuxfoundation$(echo .)org \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=gnurou@gmail$(echo .)com \
    --cc=linus.walleij@linaro$(echo .)org \
    --cc=linux-gpio@vger$(echo .)kernel.org \
    --cc=linux-iio@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-watchdog@vger$(echo .)kernel.org \
    --cc=linux@roeck-us$(echo .)net \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=vilhelm.gray@gmail$(echo .)com \
    --cc=x86@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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