mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yinghai Lu <yhlu.kernel@gmail.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-acpi@vger.kernel.org
Subject: Re: [PATCH 5/7] x86/PCI: print resources consistently with %pRt
Date: Wed, 7 Oct 2009 11:43:09 -0700	[thread overview]
Message-ID: <86802c440910071143y7ba8b0f8y9efff738eba9d30b@mail.gmail.com> (raw)
In-Reply-To: <20091006213349.4272.65914.stgit@bob.kio>

On Tue, Oct 6, 2009 at 2:33 PM, Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> This uses %pRt to print additional resource information (type, size,
> prefetchability, etc.) consistently.
>
> Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
> ---
>  arch/x86/pci/acpi.c |   14 +++++++++++---
>  arch/x86/pci/i386.c |   12 +++++-------
>  2 files changed, 16 insertions(+), 10 deletions(-)
>
> diff --git a/arch/x86/pci/acpi.c b/arch/x86/pci/acpi.c
> index 2297280..4d4f1df 100644
> --- a/arch/x86/pci/acpi.c
> +++ b/arch/x86/pci/acpi.c
> @@ -7,6 +7,7 @@
>  #include <asm/pci_x86.h>
>
>  struct pci_root_info {
> +       struct acpi_device *bridge;
>        char *name;
>        unsigned int res_num;
>        struct resource *res;
> @@ -107,12 +108,18 @@ setup_resource(struct acpi_resource *acpi_res, void *data)
>        res->child = NULL;
>
>        if (insert_resource(root, res)) {
> -               printk(KERN_ERR "PCI: Failed to allocate 0x%lx-0x%lx "
> -                       "from %s for %s\n", (unsigned long) res->start,
> -                       (unsigned long) res->end, root->name, info->name);
> +               dev_err(&info->bridge->dev, "can't allocate %pRt\n", res);

better to keep that root name ?

YH

  reply	other threads:[~2009-10-07 18:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06 21:33 [PATCH 0/7] PCI, PNP: print resources consistently Bjorn Helgaas
2009-10-06 21:33 ` [PATCH 1/7] vsprintf: fix io/mem resource width Bjorn Helgaas
2009-10-26 20:40   ` Jesse Barnes
2009-10-06 21:33 ` [PATCH 2/7] vsprintf: add %pR support for IRQ and DMA resources Bjorn Helgaas
2009-10-06 21:33 ` [PATCH 3/7] vsprintf: add %pRt, %pRf to print struct resource details Bjorn Helgaas
2009-10-06 21:33 ` [PATCH 4/7] PCI: print resources consistently with %pRt Bjorn Helgaas
2009-10-06 21:33 ` [PATCH 5/7] x86/PCI: " Bjorn Helgaas
2009-10-07 18:43   ` Yinghai Lu [this message]
2009-10-07 19:15     ` Bjorn Helgaas
2009-10-09 21:14       ` Len Brown
2009-10-10 15:36         ` Bjorn Helgaas
2009-10-06 21:33 ` [PATCH 6/7] ia64/PCI: " Bjorn Helgaas
2009-10-06 21:34 ` [PATCH 7/7] PNP: " 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=86802c440910071143y7ba8b0f8y9efff738eba9d30b@mail.gmail.com \
    --to=yhlu.kernel@gmail.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@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

all inboxes | Powered by JetHome®