The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alexander Usyskin <alexander.usyskin@intel.com>
Cc: Reuven Abliyev <reuven.abliyev@intel.com>, linux-kernel@vger.kernel.org
Subject: Re: [char-misc-next v2 4/5] mei: more prints with client prefix
Date: Mon, 30 Jun 2025 19:25:39 +0200	[thread overview]
Message-ID: <2025063003-doable-magician-3218@gregkh> (raw)
In-Reply-To: <20250630091942.2116676-5-alexander.usyskin@intel.com>

On Mon, Jun 30, 2025 at 12:19:41PM +0300, Alexander Usyskin wrote:
> Use client-aware print macro instead of
> usual device print in more places.

Why?  This changes the output of the driver.

> 
> Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
> ---
>  drivers/misc/mei/hbm.c       | 14 ++++-----
>  drivers/misc/mei/interrupt.c |  2 +-
>  drivers/misc/mei/main.c      | 55 +++++++++++++++++-------------------
>  3 files changed, 34 insertions(+), 37 deletions(-)
> 
> diff --git a/drivers/misc/mei/hbm.c b/drivers/misc/mei/hbm.c
> index 026b1f686c16..4fe9a2752d43 100644
> --- a/drivers/misc/mei/hbm.c
> +++ b/drivers/misc/mei/hbm.c
> @@ -510,7 +510,7 @@ int mei_hbm_cl_notify_req(struct mei_device *dev,
>  
>  	ret = mei_hbm_write_message(dev, &mei_hdr, &req);
>  	if (ret)
> -		dev_err(dev->dev, "notify request failed: ret = %d\n", ret);
> +		cl_err(dev, cl, "notify request failed: ret = %d\n", ret);

Why do you have a mei-specific debug printk macro anyway?  You really
shouldn't do that :(

This feels like a step backwards.

thanks,

greg k-h

  reply	other threads:[~2025-06-30 17:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-30  9:19 [char-misc-next v2 0/5] mei: fix mei_device lifetime Alexander Usyskin
2025-06-30  9:19 ` [char-misc-next v2 1/5] mei: set parent for char device Alexander Usyskin
2025-06-30 10:02   ` Greg Kroah-Hartman
2025-06-30 13:02     ` Usyskin, Alexander
2025-06-30 13:13       ` Greg Kroah-Hartman
2025-07-16  7:44         ` Usyskin, Alexander
2025-07-16  7:47           ` Greg Kroah-Hartman
2025-07-16  8:09             ` Usyskin, Alexander
2025-06-30  9:19 ` [char-misc-next v2 2/5] mei: make char device control its own lifetime Alexander Usyskin
2025-06-30 17:24   ` Greg Kroah-Hartman
2025-06-30  9:19 ` [char-misc-next v2 3/5] mei: bus: use cldev in prints Alexander Usyskin
2025-06-30  9:19 ` [char-misc-next v2 4/5] mei: more prints with client prefix Alexander Usyskin
2025-06-30 17:25   ` Greg Kroah-Hartman [this message]
2025-07-01 10:13     ` Usyskin, Alexander
2025-06-30  9:19 ` [char-misc-next v2 5/5] mei: create dedicated device object Alexander Usyskin
2025-06-30 17:27   ` Greg Kroah-Hartman
2025-07-01 10:55     ` Usyskin, Alexander
2025-06-30 10:02 ` [char-misc-next v2 0/5] mei: fix mei_device lifetime Greg Kroah-Hartman

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=2025063003-doable-magician-3218@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=alexander.usyskin@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reuven.abliyev@intel.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