From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Matan Azrad <matan@mellanox.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/vdev_netvsc: get rid of unnecessary debug log message
Date: Tue, 27 Nov 2018 16:26:46 +0000 [thread overview]
Message-ID: <17fb9c2a-186c-a4c9-0730-5b03ff2ac900@intel.com> (raw)
In-Reply-To: <AM0PR0502MB401947AF3660446D8FBA3AEED2D00@AM0PR0502MB4019.eurprd05.prod.outlook.com>
On 11/27/2018 4:18 PM, Matan Azrad wrote:
>
>
> From: Stephen Hemminger
>> If vdev_netvsc is run with debug logging enabled, then the log output will fill
>> with:
>> net_vdev_netvsc: interface lo is non-ethernet device
>>
>> Remove the message since it is not useful.
>>
>> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> Acked-by: Matan Azrad <matan@mellanox.com>
>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-11-27 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 21:13 Stephen Hemminger
2018-11-27 16:18 ` Matan Azrad
2018-11-27 16: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=17fb9c2a-186c-a4c9-0730-5b03ff2ac900@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.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).