DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 0/7] Remove some uses of PMD logtype
Date: Tue, 31 Mar 2020 18:43:09 +0100	[thread overview]
Message-ID: <99a03dba-f888-0005-f8f9-0381a398b730@intel.com> (raw)
In-Reply-To: <20200331173110.25746-1-stephen@networkplumber.org>

On 3/31/2020 6:31 PM, Stephen Hemminger wrote:
> While working on netvsc driver, noticed that there are still some places
> in some drivers using the old PMD static logtype.  Would like to
> eradicate all of these and even mark it as deprecated in a future
> release.
> 
> v2 - fix checkpatch whitespace complaints

Hi Stephen,

I have applied the v1 and fixed the whitespace complaints while merging, is
there anything else changed in v2?

> 
> Stephen Hemminger (7):
>   net/mvneta: do not use PMD logtype
>   net/virtio: do not use PMD logtype
>   net/tap: do not use PMD logtype
>   net/pfe: do not use PMD logtype
>   net/bnxt: don't use PMD logtype
>   net/dpaa: use dynamic logtype
>   net/thunderx: use dynamic logtype
> 
>  drivers/net/bnxt/bnxt_ring.c            |  2 +-
>  drivers/net/dpaa/dpaa_ethdev.c          | 23 ++++++++---------------
>  drivers/net/mvneta/mvneta_ethdev.c      |  2 +-
>  drivers/net/pfe/pfe_ethdev.c            |  4 ++--
>  drivers/net/tap/rte_eth_tap.c           |  6 ++++--
>  drivers/net/thunderx/nicvf_ethdev.c     | 17 +++++++++--------
>  drivers/net/virtio/virtio_rxtx.c        |  6 +++---
>  drivers/net/virtio/virtio_user_ethdev.c |  2 +-
>  8 files changed, 29 insertions(+), 33 deletions(-)
> 


  parent reply	other threads:[~2020-03-31 17:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31  4:41 [dpdk-dev] [PATCH 0/7] Remove " Stephen Hemminger
2020-03-31  4:41 ` [dpdk-dev] [PATCH 1/7] net/mvneta: do not use " Stephen Hemminger
2020-03-31  4:41 ` [dpdk-dev] [PATCH 2/7] net/virtio: " Stephen Hemminger
2020-03-31  4:41 ` [dpdk-dev] [PATCH 3/7] net/tap: " Stephen Hemminger
2020-03-31  4:41 ` [dpdk-dev] [PATCH 4/7] net/pfe: " Stephen Hemminger
2020-03-31  4:41 ` [dpdk-dev] [PATCH 5/7] net/bnxt: don't " Stephen Hemminger
2020-03-31  4:43   ` Somnath Kotur
2020-03-31  4:41 ` [dpdk-dev] [PATCH 6/7] net/dpaa: use dynamic logtype Stephen Hemminger
2020-03-31  4:41 ` [dpdk-dev] [PATCH 7/7] net/thunderx: " Stephen Hemminger
2020-03-31 17:31 ` [dpdk-dev] [PATCH v2 0/7] Remove some uses of PMD logtype Stephen Hemminger
2020-03-31 17:31   ` [dpdk-dev] [PATCH v2 1/7] net/mvneta: do not use " Stephen Hemminger
2020-03-31 17:31   ` [dpdk-dev] [PATCH v2 2/7] net/virtio: " Stephen Hemminger
2020-03-31 17:31   ` [dpdk-dev] [PATCH v2 3/7] net/tap: " Stephen Hemminger
2020-03-31 17:31   ` [dpdk-dev] [PATCH v2 4/7] net/pfe: " Stephen Hemminger
2020-03-31 17:31   ` [dpdk-dev] [PATCH v2 5/7] net/bnxt: don't " Stephen Hemminger
2020-03-31 17:31   ` [dpdk-dev] [PATCH v2 6/7] net/dpaa: use dynamic logtype Stephen Hemminger
2020-03-31 17:31   ` [dpdk-dev] [PATCH v2 7/7] net/thunderx: " Stephen Hemminger
2020-03-31 17:43   ` Ferruh Yigit [this message]
2020-03-31 17:49     ` [dpdk-dev] [PATCH v2 0/7] Remove some uses of PMD logtype Ferruh Yigit
2020-03-31 17:42 ` [dpdk-dev] [PATCH 0/7] Remove " Ferruh Yigit

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=99a03dba-f888-0005-f8f9-0381a398b730@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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).