From: Bjorn Helgaas <bhelgaas@google.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Matt Fleming <matt.fleming@intel.com>,
Matthew Garrett <mjg59@srcf.ucam.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] PCI updates for v3.10
Date: Thu, 6 Jun 2013 11:38:03 -0600 [thread overview]
Message-ID: <CAErSpo7fvMDFHP2BcDGeOrjFaqRYf+d_0YwHyX3ccgrkpXaTyA@mail.gmail.com> (raw)
In-Reply-To: <20130606173419.GA8186@google.com>
[+cc linux-pci, linux-kernel]
On Thu, Jun 6, 2013 at 11:34 AM, Bjorn Helgaas <bhelgaas@google.com> wrote:
> Hi Linus,
>
> Here's another fix for v3.10. This fixes a crash when booting a 32-bit
> kernel via the EFI boot stub.
>
> Bjorn
>
>
> The following changes since commit f3f011750a18abc389ef1b0d504fbeeacf641919:
>
> Revert "x86/pci/mrst: Use configuration mechanism 1 for 00:00.0, 00:02.0, 00:03.0" (2013-05-20 10:20:21 -0600)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git tags/pci-v3.10-fixes-3
>
> for you to fetch changes up to 65694c5aaddfedd9da082e4e150cafc6b3fc8a6a:
>
> x86/PCI: Map PCI setup data with ioremap() so it can be in highmem (2013-06-05 10:50:04 -0600)
>
> ----------------------------------------------------------------
> PCI update for v3.10:
>
> PCI ROM from EFI
> x86/PCI: Map PCI setup data with ioremap() so it can be in highmem
>
> ----------------------------------------------------------------
> Matt Fleming (1):
> x86/PCI: Map PCI setup data with ioremap() so it can be in highmem
>
> arch/x86/pci/common.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
next parent reply other threads:[~2013-06-06 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130606173419.GA8186@google.com>
2013-06-06 17:38 ` Bjorn Helgaas [this message]
2013-05-23 20:09 Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2013-05-09 16:46 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=CAErSpo7fvMDFHP2BcDGeOrjFaqRYf+d_0YwHyX3ccgrkpXaTyA@mail.gmail.com \
--to=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mjg59@srcf.ucam.org \
--cc=torvalds@linux-foundation.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®