mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: William Breathitt Gray <vilhelm.gray@gmail.com>
Cc: mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
	gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] base: isa: Remove X86_32 dependency
Date: Mon, 22 Feb 2016 19:39:36 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.11.1602221939050.2477@nanos> (raw)
In-Reply-To: <56CA9016.3080108@gmail.com>

On Sun, 21 Feb 2016, William Breathitt Gray wrote:

> On 01/27/2016 05:07 AM, Thomas Gleixner wrote:
> > On Fri, 22 Jan 2016, William Breathitt Gray wrote:
> >> Many motherboards utilize a LPC to ISA bridge in order to decode
> >> ISA-style port-mapped I/O addresses. This is particularly true for
> >> embedded motherboards supporting the PC/104 bus (a bus specification
> >> derived from ISA).
> >>
> >> These motherboards are now commonly running 64-bit x86 processors. The
> >> X86_32 dependency should be removed from the ISA bus configuration
> >> option in order to support these newer motherboards.
> >>
> >> A new config option, CONFIG_ISA_BUS, is introduced to allow for the
> >> compilation of the ISA bus driver independent of the CONFIG_ISA option.
> >> Devices which communicate via ISA-compatible buses can now be supported
> >> independent of the dependencies of the CONFIG_ISA option.
> >>
> >> Signed-off-by: William Breathitt Gray <vilhelm.gray@gmail.com>
> > 
> > Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
> 
> What more can I do to help get this patch pulled in for the merge
> window?

If Greg doesn't pick it up, I'll pull it into x86 later this week

Thanks,

	tglx

  reply	other threads:[~2016-02-22 18:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-22 16:28 William Breathitt Gray
2016-01-27 10:07 ` Thomas Gleixner
2016-02-22  4:35   ` William Breathitt Gray
2016-02-22 18:39     ` Thomas Gleixner [this message]
2016-02-22 19:31       ` Greg KH

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=alpine.DEB.2.11.1602221939050.2477@nanos \
    --to=tglx@linutronix.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=vilhelm.gray@gmail.com \
    --cc=x86@kernel.org \
    /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

all inboxes | Powered by JetHome®