DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Venkatesh Vemula <venkatesh.vemula@intel.com>
Cc: <dev@dpdk.org>, <aman.deep.singh@intel.com>,
	<shaiq.wani@intel.com>, <david.marchand@redhat.com>
Subject: Re: [PATCH v7 2/2] net/cpfl: added CPFL devID for MMG
Date: Tue, 14 Oct 2025 13:48:51 +0100	[thread overview]
Message-ID: <aO5Gs9gOiTmgBSOW@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20251014104511.459215-3-venkatesh.vemula@intel.com>

On Tue, Oct 14, 2025 at 04:15:11PM +0530, Venkatesh Vemula wrote:
> CPFL changes added to new CPFL device id for MMG.
> rebased to next-net-intel-for-next-net and fixed conflict
> and compiler issue.
> changed macro name IDPF_DEVICE_ID_CPF to CPFL_DEV_ID_MEV
> 
> Signed-off-by: Venkatesh Vemula <venkatesh.vemula@intel.com>
> ---
Acked-by: Bruce Richardson <bruce.richardson@intel.com>


>  .mailmap                             |  1 +
>  drivers/net/intel/cpfl/cpfl_ethdev.c | 13 +++++++------
>  drivers/net/intel/cpfl/cpfl_ethdev.h |  5 +++--
>  3 files changed, 11 insertions(+), 8 deletions(-)
> 
> diff --git a/.mailmap b/.mailmap
> index 0dcd8fce3a..7c121cf5ba 100644
> --- a/.mailmap
> +++ b/.mailmap
> @@ -1665,6 +1665,7 @@ Venkata Suresh Kumar P <venkata.suresh.kumar.p@intel.com>
>  Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com>
>  Venkatesh Nuthula <venki497@gmail.com>
>  Venkatesh Srinivas <venkateshs@google.com>
> +Venkatesh Vemula <venkatesh.vemula@intel.com>
>  Venkateshwarlu Nalla <venkatn@marvell.com>
>  Venkat Koppula <venkat.koppula@caviumnetworks.com>
>  Venkat Kumar Ande <venkatkumar.ande@amd.com>

Mailmap change should be in the first patch of the set. I'll probably
change the patch order on apply to fix this.


  reply	other threads:[~2025-10-14 12:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-19 14:51 [PATCH v1] net/idpf: add IDPF PCI class ID support Vemula Venkatesh
2025-09-22  8:31 ` Wani, Shaiq
2025-09-22 12:09 ` David Marchand
2025-09-22 16:35   ` Singh, Aman Deep
2025-09-23  6:52     ` David Marchand
2025-09-24 12:57 ` [PATCH v2] net/intel: " Vemula Venkatesh
2025-09-24 14:34   ` Bruce Richardson
2025-09-25 10:28     ` Vemula, Venkatesh
2025-09-25 17:47   ` [PATCH v3] " Vemula Venkatesh
2025-09-26 15:26     ` Singh, Aman Deep
2025-09-29 14:00 ` [PATCH v4] " Vemula Venkatesh
2025-10-01 15:30 ` [PATCH v5] " Vemula Venkatesh
2025-10-06 18:12 ` [PATCH v6] " Venkatesh Vemula
2025-10-09 16:10   ` Bruce Richardson
2025-10-14 10:20 ` [PATCH v7 0/2] " Venkatesh Vemula
2025-10-14 10:20   ` [PATCH v7 1/2] net/idpf: " Venkatesh Vemula
2025-10-14 10:20   ` [PATCH v7 2/2] net/cpfl: added CPFL devID for MMG Venkatesh Vemula
2025-10-14 10:44 ` [PATCH v7 0/2] net/intel: add IDPF PCI class ID support Venkatesh Vemula
2025-10-14 10:45 ` Venkatesh Vemula
2025-10-14 10:45   ` [PATCH v7 1/2] net/idpf: " Venkatesh Vemula
2025-10-14 12:47     ` Bruce Richardson
2025-10-14 13:24       ` Bruce Richardson
2025-10-14 10:45   ` [PATCH v7 2/2] net/cpfl: added CPFL devID for MMG Venkatesh Vemula
2025-10-14 12:48     ` Bruce Richardson [this message]
2025-10-14 13:34       ` Vemula, Venkatesh

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=aO5Gs9gOiTmgBSOW@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=aman.deep.singh@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=shaiq.wani@intel.com \
    --cc=venkatesh.vemula@intel.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).