From: okaya@codeaurora.org (Sinan Kaya)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] PCI: move early dump functionality from x86 arch into the common code
Date: Fri, 1 Jun 2018 14:58:48 -0400 [thread overview]
Message-ID: <dac3d600-86c4-456a-046b-f2229a8c19d7@codeaurora.org> (raw)
In-Reply-To: <20180601185310.GA175802@bhelgaas-glaptop.roam.corp.google.com>
On 6/1/2018 2:53 PM, Bjorn Helgaas wrote:
>> + pci_info(pdev, "pci 0000:%02x:%02x.%d config space:\n",
>> + pdev->bus->number, PCI_SLOT(pdev->devfn),
>> + PCI_FUNC(pdev->devfn));
> I'm still missing something -- why go to the trouble of pdev->bus->number,
> PCI_SLOT(), etc? Isn't the output going to look like this?
>
> pci 0000:00:00.0: pci 0000:00:00.0 config space:
>
> In other words, wouldn't the following be enough?
>
> pci_info(pdev, "config space:\n");
>
You are right. The origin print function was pr_info. We don't need that
stuff anymore.
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
prev parent reply other threads:[~2018-06-01 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 18:47 [PATCH V2] PCI: move early dump functionality from x86 arch into the common code Sinan Kaya
2018-06-01 18:53 ` Bjorn Helgaas
2018-06-01 18:58 ` Sinan Kaya [this message]
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=dac3d600-86c4-456a-046b-f2229a8c19d7@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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