[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210422134302.GA1388@agape.jhs>
Date: Thu, 22 Apr 2021 15:43:04 +0200
From: Fabio Aiuto <fabioaiuto83@...il.com>
To: Deepak R Varma <drv@...lo.com>
Cc: Mauro Carvalho Chehab <mchehab@...nel.org>,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-media@...r.kernel.org, linux-staging@...ts.linux.dev,
linux-kernel@...r.kernel.org, mh12gx2825@...il.com
Subject: Re: [PATCH] staging: media: atomisp: replace pr_info() by dev_info()
On Thu, Apr 22, 2021 at 04:00:37PM +0530, Deepak R Varma wrote:
> It is recommended to use driver model diagnostic macros dev_*() instead
> of pr_*() since the former ensures that the log messages are always
> associated with the corresponding device and driver.
>
> Suggested-by: Fabio Aiuto <fabioaiuto83@...il.com>
> Signed-off-by: Deepak R Varma <drv@...lo.com>
> ---
>
> Note: There are few more pr_into() calls that I have not replaced since
> they are very basic (entry and exit) and temporary. They can be removed
> if the APIs are fully tested. See this example:
> pr_info("%s S\n", __func__);
>
> Let me know if I should remove them and resubmit this patch.
>
Hi Deepak,
usually log functions saying "we are here in the code" are not needed,
ftrace is designed for function tracing and other useful things.
I think this patch is aimed for substitution which is logically
different from deletion of function calls.
pr_info deletions can be provided in a separate patch.
Thank you,
fabio
Powered by blists - more mailing lists