From: Thomas Monjalon <thomas@monjalon.net>
To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: dev@dpdk.org, david.marchand@redhat.com
Subject: Re: [dpdk-dev] [pull-request] dpdk-next-eventdev - v21.11 - RC1
Date: Thu, 21 Oct 2021 20:53:32 +0200 [thread overview]
Message-ID: <1830763.Vca4t2WveJ@thomas> (raw)
In-Reply-To: <BY3PR18MB4785ED7B5529611C497EB99CC8BE9@BY3PR18MB4785.namprd18.prod.outlook.com>
20/10/2021 20:29, Jerin Jacob Kollanukkaran:
> http://dpdk.org/git/next/dpdk-next-eventdev
Pulled, thanks.
Note: I took care of consistency in commit titles
and noticed the new prefix /rx_adapater.
I decided to go with /eth_rx which maps the file names
and applied the same logic for /crypto and /timer adapters.
prev parent reply other threads:[~2021-10-21 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 18:29 Jerin Jacob Kollanukkaran
2021-10-21 18:53 ` Thomas Monjalon [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=1830763.Vca4t2WveJ@thomas \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@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).