From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: Somnath Kotur <somnath.kotur@broadcom.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/3] bnxt: logging cleanups
Date: Fri, 15 Mar 2019 18:29:28 +0000 [thread overview]
Message-ID: <ca0720de-2d4a-cead-5b01-b025a9179cce@intel.com> (raw)
Message-ID: <20190315182928.uitfQnCgrcZK1vyPWEkWQY7mkC0DWueLMicoqru3uXQ@z> (raw)
In-Reply-To: <CACZ4nhtZ6C1ixMU8VuFNcoYZ0ruPt8vSQ7YtyL4-hyO3NEy=Fw@mail.gmail.com>
On 3/11/2019 6:19 PM, Ajit Khaparde wrote:
> On Mon, Mar 11, 2019 at 11:11 AM Stephen Hemminger <
> stephen@networkplumber.org> wrote:
>
>> This reduces the logging in this driver and makes it
>> work like others.
>>
>> Stephen Hemminger (3):
>> net/bnxt: change PTP message to DEBUG level
>> net/bnxt: do not double space version message
>> net/bnxt: use NOTICE as default log level
>>
> Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
Series applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2019-03-15 18:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 18:11 Stephen Hemminger
2019-03-11 18:11 ` [dpdk-dev] [PATCH 1/3] net/bnxt: change PTP message to DEBUG level Stephen Hemminger
2019-03-11 18:11 ` [dpdk-dev] [PATCH 2/3] net/bnxt: do not double space version message Stephen Hemminger
2019-03-11 18:11 ` [dpdk-dev] [PATCH 3/3] net/bnxt: use NOTICE as default log level Stephen Hemminger
2019-03-11 18:19 ` [dpdk-dev] [PATCH 0/3] bnxt: logging cleanups Ajit Khaparde
2019-03-15 18:29 ` Ferruh Yigit [this message]
2019-03-15 18:29 ` 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=ca0720de-2d4a-cead-5b01-b025a9179cce@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=somnath.kotur@broadcom.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).