From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: [dpdk-dev] Time to kill RTE_LOGTYPE_PMD?
Date: Wed, 10 Jul 2019 12:50:26 -0700 [thread overview]
Message-ID: <20190710125026.109629ca@hermes.lan> (raw)
The old "Poll Mode Driver" PMD log type should not be used in current DPDK
but lots of drivers still are. The PMD log level should purged.
Could the driver writers please fix it (or I will do it for them).
drivers/bus/dpaa/rte_dpaa_logs.h
drivers/bus/fslmc/fslmc_logs.h
drivers/common/cpt/cpt_pmd_logs.h
drivers/common/dpaax/dpaax_logs.h
drivers/common/octeontx2/otx2_common.h
drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c
drivers/crypto/armv8/rte_armv8_pmd.c
drivers/crypto/caam_jr/caam_jr.c
drivers/crypto/caam_jr/caam_jr_log.h
drivers/crypto/ccp/rte_ccp_pmd.c
drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
drivers/crypto/dpaa2_sec/dpaa2_sec_logs.h
drivers/crypto/dpaa2_sec/hw/compat.h
drivers/crypto/dpaa_sec/dpaa_sec.c
drivers/crypto/dpaa_sec/dpaa_sec_log.h
drivers/crypto/scheduler/scheduler_pmd.c
drivers/event/dpaa2/dpaa2_eventdev.c
drivers/event/dpaa2/dpaa2_eventdev_logs.h
drivers/event/skeleton/skeleton_eventdev.c
drivers/event/skeleton/skeleton_eventdev.h
drivers/mempool/dpaa2/dpaa2_hw_mempool.c
drivers/mempool/dpaa2/dpaa2_hw_mempool_logs.h
drivers/net/ark/ark_logs.h
drivers/net/atlantic/atl_logs.h
drivers/net/avp/avp_logs.h
drivers/net/bnxt/bnxt_ring.c
drivers/net/bnxt/bnxt_rxtx_vec_sse.c
drivers/net/bnxt/bnxt_txr.c
drivers/net/bonding/rte_eth_bond_args.c
drivers/net/cxgbe/cxgbe_compat.h
drivers/net/dpaa2/dpaa2_ethdev.c
drivers/net/dpaa2/dpaa2_pmd_logs.h
drivers/net/dpaa/dpaa_ethdev.c
drivers/net/e1000/e1000_logs.h
drivers/net/ena/base/ena_plat_dpdk.h
drivers/net/ena/ena_ethdev.c
drivers/net/ena/ena_logs.h
drivers/net/enetc/enetc_logs.h
drivers/net/enic/enic_compat.h
drivers/net/fm10k/fm10k_logs.h
drivers/net/i40e/i40e_logs.h
drivers/net/iavf/iavf_log.h
drivers/net/ice/ice_logs.h
drivers/net/ifc/base/ifcvf_osdep.h
drivers/net/ixgbe/ixgbe_logs.h
drivers/net/ixgbe/ixgbe_pf.c
drivers/net/mvneta/mvneta_ethdev.c
drivers/net/mvpp2/mrvl_ethdev.c
drivers/net/nfb/nfb_ethdev.c
drivers/net/nfb/nfb_rx.c
drivers/net/nfb/nfb_rx.h
drivers/net/nfb/nfb_tx.c
drivers/net/nfb/nfb_tx.h
drivers/net/nfp/nfpcore/nfp_cpp_pcie_ops.c
drivers/net/nfp/nfp_net.c
drivers/net/nfp/nfp_net_logs.h
drivers/net/octeontx/octeontx_ethdev.c
drivers/net/qede/qede_logs.h
drivers/net/tap/rte_eth_tap.c
drivers/net/thunderx/nicvf_ethdev.c
drivers/net/virtio/virtio_logs.h
drivers/net/virtio/virtio_rxtx.c
drivers/net/virtio/virtio_user_ethdev.c
drivers/net/vmxnet3/vmxnet3_logs.h
drivers/raw/dpaa2_cmdif/dpaa2_cmdif_logs.h
drivers/raw/dpaa2_qdma/dpaa2_qdma_logs.h
drivers/raw/ifpga_rawdev/base/osdep_rte/osdep_generic.h
examples/fips_validation/fips_dev_self_test.c
reply other threads:[~2019-07-10 19:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190710125026.109629ca@hermes.lan \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.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).