From: Bjorn Helgaas <helgaas@kernel.org>
To: fred@fredlawl.com
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
mika.westerberg@linux.intel.com, lukas@wunner.de,
andriy.shevchenko@linux.intel.com, keith.busch@intel.com,
mr.nuke.me@gmail.com, liudongdong3@huawei.com,
thesven73@gmail.com
Subject: Re: [PATCH 1/4] PCI: Replace dev_*() printk wrappers with pci_*() printk wrappers
Date: Sun, 28 Apr 2019 19:52:22 -0500 [thread overview]
Message-ID: <20190429005222.GO14616@google.com> (raw)
In-Reply-To: <20190429000258.GK14616@google.com>
On Sun, Apr 28, 2019 at 07:02:58PM -0500, Bjorn Helgaas wrote:
> On Sat, Apr 27, 2019 at 02:13:01PM -0500, fred@fredlawl.com wrote:
> > From: Frederick Lawler <fred@fredlawl.com>
> >
> > Replace remaining instances of dev_*() printk wrappers with pci_*()
> > printk wrappers. No functional change intended.
> >
> > Signed-off-by: Frederick Lawler <fred@fredlawl.com>
> > ---
> > drivers/pci/pcie/aer.c | 13 ++++++-------
> > drivers/pci/pcie/aer_inject.c | 4 ++--
> > drivers/pci/pcie/dpc.c | 27 ++++++++++++---------------
> > 3 files changed, 20 insertions(+), 24 deletions(-)
> > aer_enable_rootport(rpc);
> > - dev_info(device, "AER enabled with IRQ %d\n", dev->irq);
> > + pci_info(pdev, "AER enabled with IRQ %d\n", dev->irq);
>
> And this, and many others below. *This* patch should only convert
>
> - pci_printk(KERN_DEBUG, pdev, ...)
> + pci_info(pdev, ...)
>
> and
>
> - dev_printk(KERN_DEBUG, pcie_dev, ...)
> + dev_info(pcie_dev, ...)
Just to clarify, I do *want* both changes, just in separate patches.
So we'd have
1) Convert KERN_DEBUG uses to pci_info() for pci_dev usage and to
dev_info() for pcie_device usage. I think pciehp is probably an
exception to this; this patch shouldn't touch ctrl_dbg().
2) Convert "dev_info(pcie_device)" to "pci_info(pci_dev)". It might
be worth doing this in separate patches for each service. If we
decide they're simple enough to combine, that's trivial for me to
do. It's a little more hassle to split things up afterwards.
In pciehp, if you do this in the ctrl_*() definitions, it will
make the patch much smaller.
3) In pciehp, ctrl_dbg() could probably be changed to use pci_dbg()
so we'd use the standard kernel dynamic debug stuff instead of
having the pciehp-specific module parameter.
Thanks a lot for working on all this. I think it will make the user
experience significantly simpler.
Bjorn
next prev parent reply other threads:[~2019-04-29 0:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-27 19:13 [PATCH 0/4] PCI: Use PCIe service name in dmesg logs fred
2019-04-27 19:13 ` [PATCH 1/4] PCI: Replace dev_*() printk wrappers with pci_*() printk wrappers fred
2019-04-28 15:43 ` Andy Shevchenko
2019-04-30 22:25 ` Frederick Lawler
2019-04-29 0:02 ` Bjorn Helgaas
2019-04-29 0:52 ` Bjorn Helgaas [this message]
2019-04-30 22:26 ` Frederick Lawler
2019-04-27 19:13 ` [PATCH 2/4] PCI: pciehp: Replace ctrl_*() with pci_*() fred
2019-04-27 20:03 ` Lukas Wunner
2019-04-29 0:36 ` Bjorn Helgaas
2019-04-27 19:13 ` [PATCH 3/4] PCI: pciehp: Remove unused macro definitions fred
2019-04-28 15:55 ` Andy Shevchenko
2019-04-29 0:13 ` Bjorn Helgaas
2019-04-27 19:13 ` [PATCH 4/4] PCI/portdrv: Add dev_fmt() to port drivers fred
2019-04-29 0:17 ` 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=20190429005222.GO14616@google.com \
--to=helgaas@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=fred@fredlawl.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liudongdong3@huawei.com \
--cc=lukas@wunner.de \
--cc=mika.westerberg@linux.intel.com \
--cc=mr.nuke.me@gmail.com \
--cc=thesven73@gmail.com \
/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).