From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Michał Krawczyk" <mk@semihalf.com>,
"Stephen Hemminger" <stephen@networkplumber.org>
Cc: Marcin Wojtas <mw@semihalf.com>,
"Tzalik, Guy" <gtzalik@amazon.com>,
"Schmeilin, Evgeny" <evgenys@amazon.com>,
dev@dpdk.org
Subject: Re: [dpdk-dev] [RFC] net/ena: use dynamic log type for debug logging
Date: Fri, 13 Sep 2019 19:46:48 +0100 [thread overview]
Message-ID: <b7d8f235-097c-85b1-2768-d6a0ddc20b30@intel.com> (raw)
In-Reply-To: <CAJMMOfO+CJm3BQ5MfKxeU1uVX2mnFe2z8yTrRx8r=M3Ox5Lscw@mail.gmail.com>
On 8/27/2019 1:51 PM, Michał Krawczyk wrote:
> wt., 16 lip 2019 o 22:43 Stephen Hemminger
> <stephen@networkplumber.org> napisał(a):
>>
>> The generic RTE_LOGTYPE_PMD is a historical relic and should
>> not be used. Every driver must use dynamic logtypes.
>>
>> Compile tested only!
>>
>> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> Tested-by: Michal Krawczyk <mk@semihalf.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2019-09-13 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 20:43 Stephen Hemminger
2019-08-27 12:51 ` Michał Krawczyk
2019-09-13 18:46 ` 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=b7d8f235-097c-85b1-2768-d6a0ddc20b30@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=evgenys@amazon.com \
--cc=gtzalik@amazon.com \
--cc=mk@semihalf.com \
--cc=mw@semihalf.com \
--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).