From: David Miller <davem@davemloft.net>
To: sudarsana.kalluru@cavium.com
Cc: netdev@vger.kernel.org, Michal.Kalderon@cavium.com
Subject: Re: [PATCH net-next 1/1] qed: Lower the severity of a dcbx log message.
Date: Sat, 01 Sep 2018 22:22:27 -0700 (PDT) [thread overview]
Message-ID: <20180901.222227.1641981458696929828.davem@davemloft.net> (raw)
In-Reply-To: <20180831111017.15747-1-sudarsana.kalluru@cavium.com>
From: Sudarsana Reddy Kalluru <sudarsana.kalluru@cavium.com>
Date: Fri, 31 Aug 2018 04:10:17 -0700
> Driver displays an error message for each unrecognized dcbx TLV that's
> received from the peer or configured on the device. It is observed that
> syslog will be flooded with such messages in certain scenarios e.g.,
> frequent link-flaps/lldp-transactions. Changing the severity of this
> message to verbose level as it's not an error scenario/message.
>
> Signed-off-by: Sudarsana Reddy Kalluru <Sudarsana.Kalluru@cavium.com>
Applied.
prev parent reply other threads:[~2018-09-02 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 11:10 [PATCH net-next 1/1] qed: Lower the severity of a dcbx log message Sudarsana Reddy Kalluru
2018-09-02 5:22 ` David Miller [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=20180901.222227.1641981458696929828.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Michal.Kalderon@cavium.com \
--cc=netdev@vger.kernel.org \
--cc=sudarsana.kalluru@cavium.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).