From: Jiri Slaby <jirislaby@gmail.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Greg KH <greg@kroah.com>,
linux-pci@atrey.karlin.mff.cuni.cz,
LKML <linux-kernel@vger.kernel.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: PCI Failed to allocate mem for PCI ROM
Date: Fri, 11 Jan 2008 17:52:17 +0100 [thread overview]
Message-ID: <47879EC1.5060508@gmail.com> (raw)
In-Reply-To: <FB6DCE73-5D8A-42AC-AE5C-0C1AD095B50B@kernel.crashing.org>
Kumar Gala napsal(a):
> I saw that patch, but if you notice that its just x86 specific and I'm
> having the issue on a powerpc 32-bit system.
My bad, sorry.
next prev parent reply other threads:[~2008-01-11 16:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 8:29 PCI Failed to allocate mem for PCI ROM Kumar Gala
2008-01-11 8:41 ` Jiri Slaby
2008-01-11 9:07 ` Kumar Gala
2008-01-11 9:13 ` Jiri Slaby
2008-01-11 15:41 ` Kumar Gala
2008-01-11 16:52 ` Jiri Slaby [this message]
2008-01-11 17:49 ` Greg KH
2008-01-11 17:50 ` Greg KH
2008-01-11 20:27 ` Kumar Gala
2008-01-12 7:27 ` Grant Grundler
2008-01-12 15:12 ` Ivan Kokshaysky
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=47879EC1.5060508@gmail.com \
--to=jirislaby@gmail.com \
--cc=galak@kernel.crashing.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linuxppc-dev@ozlabs.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).