From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Harman Kalra <hkalra@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH] maintainers: update for OCTEONTX
Date: Thu, 12 Dec 2019 10:54:12 +0000 [thread overview]
Message-ID: <7f63649f-016c-3bd1-228d-3f6fe36fa8fc@intel.com> (raw)
In-Reply-To: <20191211152710.GA152154@outlook.office365.com>
On 12/11/2019 3:27 PM, Harman Kalra wrote:
> On Wed, Dec 11, 2019 at 07:53:42PM +0530, jerinj@marvell.com wrote:
>> From: Jerin Jacob <jerinj@marvell.com>
>>
>> Harman thankfully accepted to replace myself as maintainer for OCTEONTX
>> ethdev PMD.
>>
>
> Acked-by: Harman Kalra <hkalra@marvell.com>
>
>> Signed-off-by: Jerin Jacob <jerinj@marvell.com>
Thanks Jerin and welcome Harman.
Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2019-12-12 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 14:23 jerinj
2019-12-11 15:27 ` Harman Kalra
2019-12-12 10:54 ` 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=7f63649f-016c-3bd1-228d-3f6fe36fa8fc@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=jerinj@marvell.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).