From: Saeed Mahameed <saeedm@nvidia.com>
To: "leon@kernel.org" <leon@kernel.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"caihuoqing@baidu.com" <caihuoqing@baidu.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH v2] net/mlx5e: Make use of mlx5_core_warn()
Date: Tue, 10 Aug 2021 08:22:03 +0000 [thread overview]
Message-ID: <d1456c73eecbe4ccb0353a275d1a48b334389bb3.camel@nvidia.com> (raw)
In-Reply-To: <YRIjoCbxAo+3SemG@unreal>
On Tue, 2021-08-10 at 09:58 +0300, Leon Romanovsky wrote:
> On Mon, Aug 09, 2021 at 08:39:10PM +0000, Saeed Mahameed wrote:
> > On Mon, 2021-08-09 at 20:19 +0800, Cai Huoqing wrote:
> > > to replace printk(KERN_WARNING ...) with mlx5_core_warn() kindly
> > > if we use mlx5_core_warn(), the prefix "mlx5:" not needed
> >
> > in mlx5e it is netdev stack so netdev_warn(priv->netdev, "foo bar");
>
> Saeed,
>
> That file is full of mlx5_core_* prints, even in the same function
> where
> Cai is changing, you will find mlx5_core_warn().
>
$ git grep -E "mlx5_core_(warn|info|err)"
drivers/net/ethernet/mellanox/mlx5/core/en_tc.c | wc -l
4
$ git grep -E "netdev_(warn|info|err)"
drivers/net/ethernet/mellanox/mlx5/core/en_tc.c | wc -l
24
4 vs 24, a big win for netdev ;-)
4 is not full. Many of mlx5 files has some leftovers historical code,
doesn't mean we need to keep the old habits ..
prev parent reply other threads:[~2021-08-10 8:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 12:19 [PATCH v2] net/mlx5e: Make use of mlx5_core_warn() Cai Huoqing
2021-08-09 12:28 ` Leon Romanovsky
2021-08-09 20:39 ` Saeed Mahameed
2021-08-10 6:58 ` Leon Romanovsky
2021-08-10 8:22 ` Saeed Mahameed [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=d1456c73eecbe4ccb0353a275d1a48b334389bb3.camel@nvidia.com \
--to=saeedm@nvidia.com \
--cc=caihuoqing@baidu.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.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