From: Bjorn Helgaas <helgaas@kernel.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Joe Perches <joe@perches.com>, Eric Auger <eric.auger@redhat.com>,
Bjorn Helgaas <bhelgaas@google.com>
Subject: [PATCH v2 0/1] vfio: Use dev_printk() when possible
Date: Sat, 30 Mar 2019 09:41:34 -0500 [thread overview]
Message-ID: <20190330144135.17351-1-helgaas@kernel.org> (raw)
From: Bjorn Helgaas <bhelgaas@google.com>
Use dev_printk() in VFIO when possible.
Changes from v1:
- Add colons after __func__ names in vfio_platform_amdxgbe.c (thanks,
Joe).
- Use the correct struct device * in vfio_platform_amdxgbe.c (thanks,
Eric).
- Use pci_printk() when we know we have a PCI device.
- Add pci_notice_ratelimited() for use in vfio_pci.c.
- Define dev_fmt in vfio_pci.c to avoid dropping the KBUILD_MODNAME
prefix when converting from pr_*() to pci_printk(). This also adds
the prefix to the places that already used dev_printk().
- Define dev_fmt in vfio_platform_common.c to avoid repeating "VFIO :" in
messages (this also adds it to a few that didn't use the prefix).
Bjorn Helgaas (1):
vfio: Use dev_printk() when possible
drivers/vfio/pci/vfio_pci.c | 26 +++++++----------
drivers/vfio/pci/vfio_pci_config.c | 28 ++++++++----------
.../platform/reset/vfio_platform_amdxgbe.c | 5 ++--
drivers/vfio/platform/vfio_platform_common.c | 12 ++++----
drivers/vfio/vfio.c | 29 +++++++++----------
include/linux/pci.h | 3 ++
6 files changed, 49 insertions(+), 54 deletions(-)
--
2.21.0.392.gf8f6787159e-goog
next reply other threads:[~2019-03-30 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-30 14:41 Bjorn Helgaas [this message]
2019-03-30 14:41 ` [PATCH 1/1] vfio: Use dev_printk() when possible Bjorn Helgaas
2019-04-02 7:53 ` Auger Eric
2019-04-23 17:35 ` Alex Williamson
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=20190330144135.17351-1-helgaas@kernel.org \
--to=helgaas@kernel.org \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=eric.auger@redhat.com \
--cc=joe@perches.com \
--cc=kvm@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).