From: Thomas Monjalon <thomas@monjalon.net>
To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: dev@dpdk.org, "McDaniel, Timothy" <timothy.mcdaniel@intel.com>
Subject: Re: [dpdk-dev] [pull-request] next-eventdev 20.11 RC4
Date: Sun, 15 Nov 2020 15:01:22 +0100 [thread overview]
Message-ID: <2681069.QIASaPK1AJ@thomas> (raw)
In-Reply-To: <BYAPR18MB2424590204FEFFC812D04F7DC8E60@BYAPR18MB2424.namprd18.prod.outlook.com>
13/11/2020 11:00, Jerin Jacob Kollanukkaran:
> http://dpdk.org/git/next/dpdk-next-eventdev
For info, I had to do some formatting fixes like:
- titles
- Coverity line should be before Fixes
- stable should not be Cc'ed if root cause is recent
Pulled, thanks.
prev parent reply other threads:[~2020-11-15 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 10:00 [dpdk-dev] [pull-request] next-eventdev 20.11 RC4 Jerin Jacob Kollanukkaran
2020-11-15 14:01 ` 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=2681069.QIASaPK1AJ@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=timothy.mcdaniel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.