DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jerin Jacob <jerinjacobk@gmail.com>, Jerin Jacob <jerinj@marvell.com>
Cc: dpdk-dev <dev@dpdk.org>,
	Nithin Dabilpuram <ndabilpuram@marvell.com>,
	Kiran Kumar K <kirankumark@marvell.com>,
	Sunil Kumar Kori <skori@marvell.com>,
	Satha Rao <skoteshwar@marvell.com>,
	Satheesh Paul <psatheesh@marvell.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/cnxk: unify file names
Date: Wed, 23 Feb 2022 12:18:02 +0000	[thread overview]
Message-ID: <f0122f01-1bd1-82d3-70d7-d233c24ecf22@intel.com> (raw)
In-Reply-To: <CALBAE1MbnwWu+apbZqUyPtMoK3Ppe6sC+4-Z2MJrBJg6uoLeqQ@mail.gmail.com>

On 2/23/2022 9:08 AM, Jerin Jacob wrote:
> On Wed, Feb 23, 2022 at 12:01 AM <jerinj@marvell.com> wrote:
>>
>> From: Jerin Jacob <jerinj@marvell.com>
>>
>> Except for the cn*_rte_flow* files, none of the other
>> file has rte in the file name, remove the
>> rte to unify the file name across the directory.
>>
>> Signed-off-by: Jerin Jacob <jerinj@marvell.com>
>> Acked-by: Kiran Kumar K <kirankumark@marvell.com>
> 
> Applied to dpdk-next-net-mrvl/for-next-net. Thanks
> 
> 

v2 updated in next-net, can you please rebase on latest next-net?

      reply	other threads:[~2022-02-23 12:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09 16:50 [dpdk-dev] [PATCH] net/cnxk: unify the file name jerinj
2022-02-18  6:18 ` Kiran Kumar Kokkilagadda
2022-02-18  7:44   ` Jerin Jacob
2022-02-22 18:32     ` Jerin Jacob
2022-02-22 18:32 ` [dpdk-dev] [PATCH v2] net/cnxk: unify file names jerinj
2022-02-23  9:08   ` Jerin Jacob
2022-02-23 12:18     ` Ferruh Yigit [this message]

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=f0122f01-1bd1-82d3-70d7-d233c24ecf22@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=jerinjacobk@gmail.com \
    --cc=kirankumark@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=psatheesh@marvell.com \
    --cc=skori@marvell.com \
    --cc=skoteshwar@marvell.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).