linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Matthew Whitehead <mwhitehe@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH 0/2] eisa: fix eisa with PCI
Date: Fri, 29 Mar 2013 09:16:16 -0600	[thread overview]
Message-ID: <CAErSpo75xgZHyUtj2vGd-iuJvL8t8mK+EA8npRP2QCMjUbZEOw@mail.gmail.com> (raw)
In-Reply-To: <1364444885-19751-1-git-send-email-yinghai@kernel.org>

[+cc linux-pci]

On Wed, Mar 27, 2013 at 10:28 PM, Yinghai Lu <yinghai@kernel.org> wrote:
> Looks like pci eisa bridge support is broken for a while.
>
> one is root io resource reference, and other one is pnp related.
>
> Please check if we can put them in v3.9.
>         eisa, PCI: Fix bus res reference
>         eisa, PCI: init eisa early before pnp step in

Both of these patches are to drivers/eisa/pci_eisa.c.  I don't see an
EISA-specific maintainer, and I caused at least one of these problems,
so I'll push these through my PCI tree unless somebody objects.

Bjorn

       reply	other threads:[~2013-03-29 15:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1364444885-19751-1-git-send-email-yinghai@kernel.org>
2013-03-29 15:16 ` Bjorn Helgaas [this message]
2013-04-01 21:09   ` [PATCH 0/2] eisa: fix eisa with PCI Bjorn Helgaas
     [not found]     ` <707419406.5567095.1364921996288.JavaMail.root@redhat.com>
     [not found]       ` <20130402172441.GA22478@google.com>
     [not found]         ` <979994016.6599283.1364940427573.JavaMail.root@redhat.com>
     [not found]           ` <20130403000731.GA27329@google.com>
     [not found]             ` <1729353177.11186718.1365018482308.JavaMail.root@redhat.com>
2013-04-03 20:07               ` Bjorn Helgaas

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=CAErSpo75xgZHyUtj2vGd-iuJvL8t8mK+EA8npRP2QCMjUbZEOw@mail.gmail.com \
    --to=bhelgaas@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mwhitehe@redhat.com \
    --cc=torvalds@linux-foundation.org \
    --cc=yinghai@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;
as well as URLs for NNTP newsgroup(s).