[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200326140353.GB20841@localhost>
Date: Thu, 26 Mar 2020 07:03:53 -0700
From: Richard Cochran <richardcochran@...il.com>
To: Grygorii Strashko <grygorii.strashko@...com>
Cc: "David S . Miller" <davem@...emloft.net>,
Lokesh Vutla <lokeshvutla@...com>,
Tony Lindgren <tony@...mide.com>, Sekhar Nori <nsekhar@...com>,
Murali Karicheri <m-karicheri2@...com>,
netdev <netdev@...r.kernel.org>, linux-omap@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v3 01/11] net: ethernet: ti: cpts: use dev_yy()
api for logs
On Fri, Mar 20, 2020 at 09:42:34PM +0200, Grygorii Strashko wrote:
> @@ -150,7 +150,7 @@ static int cpts_fifo_read(struct cpts *cpts, int match)
> break;
>
> if (list_empty(&cpts->pool) && cpts_purge_events(cpts)) {
> - pr_err("cpts: event pool empty\n");
> + dev_info(cpts->dev, "cpts: event pool empty\n");
You changed err into info. Was that on purpose?
The size of the pool is hard coded, but it should be large enough for
any use case. If the pool size turns out to be too small at run time,
then I think the message deserves at least the level of warning.
Thanks,
Richard
Powered by blists - more mailing lists