From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/3] leftover INIT_DEBUG stuff
Date: Mon, 15 Oct 2018 11:10:24 +0100 [thread overview]
Message-ID: <91c573f5-ee47-6652-6e65-799c99882462@intel.com> (raw)
In-Reply-To: <20181012234252.29049-1-stephen@networkplumber.org>
On 10/13/2018 12:42 AM, Stephen Hemminger wrote:
> Was looking around and found some leftover references to
> old INIT_DEBUG configurations.
>
> Stephen Hemminger (3):
> doc: remove INIT_DEBUG from ena
> doc: liquidio remove documentation for old config options
> qede: remove #ifdef for INIT_DEBUG
For series,
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2018-10-15 10:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 23:42 Stephen Hemminger
2018-10-12 23:42 ` [dpdk-dev] [PATCH 1/3] doc: remove INIT_DEBUG from ena Stephen Hemminger
2018-10-12 23:42 ` [dpdk-dev] [PATCH 2/3] doc: liquidio remove documentation for old config options Stephen Hemminger
2018-10-12 23:42 ` [dpdk-dev] [PATCH 3/3] qede: remove #ifdef for INIT_DEBUG Stephen Hemminger
2018-10-15 10:10 ` Ferruh Yigit [this message]
2018-10-15 10:13 ` [dpdk-dev] [PATCH 0/3] leftover INIT_DEBUG stuff Ferruh Yigit
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=91c573f5-ee47-6652-6e65-799c99882462@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/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).