From: Alex Williamson <alex.williamson@redhat.com>
To: kvm@vger.kernel.org
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
dev@dpdk.org, mtosatti@redhat.com, thomas@monjalon.net,
bluca@debian.org, jerinjacobk@gmail.com,
bruce.richardson@intel.com, cohuck@redhat.com
Subject: [dpdk-dev] [PATCH v2 6/7] vfio/pci: Remove dev_fmt definition
Date: Wed, 19 Feb 2020 11:54:36 -0700 [thread overview]
Message-ID: <158213847608.17090.2262660641448703487.stgit@gimli.home> (raw)
In-Reply-To: <158213716959.17090.8399427017403507114.stgit@gimli.home>
It currently results in messages like:
"vfio-pci 0000:03:00.0: vfio_pci: ..."
Which is quite a bit redundant.
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
---
drivers/vfio/pci/vfio_pci.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/vfio/pci/vfio_pci.c b/drivers/vfio/pci/vfio_pci.c
index b40ade48a844..497ecadef2ba 100644
--- a/drivers/vfio/pci/vfio_pci.c
+++ b/drivers/vfio/pci/vfio_pci.c
@@ -9,7 +9,6 @@
*/
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
-#define dev_fmt pr_fmt
#include <linux/device.h>
#include <linux/eventfd.h>
next prev parent reply other threads:[~2020-02-19 18:55 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 18:53 [dpdk-dev] [PATCH v2 0/7] vfio/pci: SR-IOV support Alex Williamson
2020-02-19 18:53 ` [dpdk-dev] [PATCH v2 1/7] vfio: Include optional device match in vfio_device_ops callbacks Alex Williamson
2020-02-19 18:54 ` [dpdk-dev] [PATCH v2 2/7] vfio/pci: Implement match ops Alex Williamson
2020-02-19 18:54 ` [dpdk-dev] [PATCH v2 3/7] vfio/pci: Introduce VF token Alex Williamson
2020-02-25 2:59 ` Tian, Kevin
2020-03-05 18:17 ` Alex Williamson
2020-03-06 8:32 ` Tian, Kevin
2020-03-06 15:39 ` Alex Williamson
2020-03-07 1:04 ` Tian, Kevin
2020-03-09 0:46 ` Alex Williamson
2020-03-09 1:22 ` Tian, Kevin
2020-03-09 1:33 ` Tian, Kevin
2020-03-09 15:35 ` Alex Williamson
2020-02-19 18:54 ` [dpdk-dev] [PATCH v2 4/7] vfio: Introduce VFIO_DEVICE_FEATURE ioctl and first user Alex Williamson
2020-02-27 17:34 ` Cornelia Huck
2020-03-05 20:51 ` Alex Williamson
2020-02-19 18:54 ` [dpdk-dev] [PATCH v2 5/7] vfio/pci: Add sriov_configure support Alex Williamson
2020-02-25 3:08 ` Tian, Kevin
2020-03-05 18:22 ` Alex Williamson
2020-03-05 20:08 ` Ajit Khaparde
2020-03-06 7:57 ` Tian, Kevin
2020-03-06 22:17 ` Alex Williamson
2020-03-07 1:35 ` Tian, Kevin
2020-03-09 0:46 ` Alex Williamson
2020-03-09 1:48 ` Tian, Kevin
2020-03-09 14:56 ` Alex Williamson
2020-03-06 9:45 ` Tian, Kevin
2020-03-06 15:50 ` Alex Williamson
2020-02-19 18:54 ` Alex Williamson [this message]
2020-02-19 18:54 ` [dpdk-dev] [PATCH v2 7/7] vfio/pci: Cleanup .probe() exit paths Alex Williamson
2020-02-25 2:33 ` [dpdk-dev] [PATCH v2 0/7] vfio/pci: SR-IOV support Tian, Kevin
2020-02-25 6:09 ` Jason Wang
2020-03-05 17:14 ` Alex Williamson
2020-03-06 3:35 ` Jason Wang
2020-03-06 16:24 ` Alex Williamson
2020-03-09 3:36 ` Jason Wang
2020-03-09 14:45 ` Alex Williamson
2020-03-05 17:33 ` Alex Williamson
2020-03-06 9:21 ` Tian, Kevin
2020-03-05 6:38 ` Vamsi Krishna Attunuru
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=158213847608.17090.2262660641448703487.stgit@gimli.home \
--to=alex.williamson@redhat.com \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=cohuck@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinjacobk@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=thomas@monjalon.net \
/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).