From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>,
jerin.jacob@caviumnetworks.com,
santosh.shukla@caviumnetworks.com, olivier.matz@6wind.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/5] Dynamic logging
Date: Tue, 9 Jan 2018 12:26:22 +0000 [thread overview]
Message-ID: <8747e828-a65b-814d-6f73-5224630ae749@intel.com> (raw)
In-Reply-To: <20171219122510.15004-1-pbhagavatula@caviumnetworks.com>
On 12/19/2017 12:25 PM, Pavan Nikhilesh wrote:
> Implement dynamic logging for cavium specific thunder nicvf and octeontx
> platforms.
>
> Pavan Nikhilesh (5):
> net/thunderx: implement dynamic logging
> net/octeontx: implement dynamic logging
> mempool/octeontx: implement dynamic logging
> event/octeontx: implement dynamic logging
> doc: remove unused config options
Series applied to dpdk-next-net/master, thanks.
(not all of them are net drivers, but getting them all to next-net to
functionally group them and updates are straightforward)
prev parent reply other threads:[~2018-01-09 12:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 12:25 Pavan Nikhilesh
2017-12-19 12:25 ` [dpdk-dev] [PATCH 1/5] net/thunderx: implement dynamic logging Pavan Nikhilesh
2018-01-01 4:36 ` santosh
2017-12-19 12:25 ` [dpdk-dev] [PATCH 2/5] net/octeontx: " Pavan Nikhilesh
2018-01-01 4:37 ` santosh
2017-12-19 12:25 ` [dpdk-dev] [PATCH 3/5] mempool/octeontx: " Pavan Nikhilesh
2018-01-01 4:39 ` santosh
2017-12-19 12:25 ` [dpdk-dev] [PATCH 4/5] event/octeontx: " Pavan Nikhilesh
2018-01-01 4:40 ` santosh
2017-12-19 12:25 ` [dpdk-dev] [PATCH 5/5] doc: remove unused config options Pavan Nikhilesh
2017-12-19 15:43 ` [dpdk-dev] [PATCH 0/5] Dynamic logging Stephen Hemminger
2018-01-09 12:26 ` 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=8747e828-a65b-814d-6f73-5224630ae749@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=olivier.matz@6wind.com \
--cc=pbhagavatula@caviumnetworks.com \
--cc=santosh.shukla@caviumnetworks.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).