From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] PCI fixes for 2.6.4-rc1
Date: Fri, 27 Feb 2004 16:09:42 -0800 [thread overview]
Message-ID: <10779269823390@kroah.com> (raw)
In-Reply-To: <20040228000725.GB13346@kroah.com>
ChangeSet 1.1613, 2004/02/24 11:07:29-08:00, rmk-pci@arm.linux.org.uk
[PATCH] PCI: Report meaningful error for failed resource allocation
pci_assign_resource reports odd messages when resource allocation fails.
This is because res->end and res->start are modified by allocate_resource.
For example:
PCI: Failed to allocate resource 1(0-ffffffff) for 0000:00:01.0
The following patch reports whether it's an IO or memory resource, and
includes the correct size. For consistency, we report it in a similar
way to the failure message in pci_request_region(), even though
res->start is unlikely to be useful.
drivers/pci/setup-res.c | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff -Nru a/drivers/pci/setup-res.c b/drivers/pci/setup-res.c
--- a/drivers/pci/setup-res.c Fri Feb 27 15:57:35 2004
+++ b/drivers/pci/setup-res.c Fri Feb 27 15:57:35 2004
@@ -143,8 +143,9 @@
}
if (ret) {
- printk(KERN_ERR "PCI: Failed to allocate resource %d(%lx-%lx) for %s\n",
- resno, res->start, res->end, pci_name(dev));
+ printk(KERN_ERR "PCI: Failed to allocate %s resource #%d:%lx@%lx for %s\n",
+ res->flags & IORESOURCE_IO ? "I/O" : "mem",
+ resno, size, res->start, pci_name(dev));
} else if (resno < PCI_BRIDGE_RESOURCES) {
pci_update_resource(dev, res, resno);
}
next prev parent reply other threads:[~2004-02-28 0:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 0:07 [BK PATCH] PCI fixes for 2.6.4-rc1 Greg KH
2004-02-28 0:09 ` Greg KH [this message]
2004-02-28 0:09 ` [PATCH] " Greg KH
2004-02-28 0:09 ` Greg KH
2004-02-28 0:09 ` Greg KH
2004-02-28 0:09 ` Greg KH
2004-02-28 0:09 ` Greg KH
2004-02-28 0:09 ` 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=10779269823390@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.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