public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: chenxingdi <chenxingdi@huawei.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "mathias.nyman@intel.com" <mathias.nyman@intel.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"chunkeey@googlemail.com" <chunkeey@googlemail.com>
Subject: 答复: [PATCH -next] usb: renesas-xhci: Use pr_info while fw verify success
Date: Wed, 27 Jul 2022 02:07:57 +0000	[thread overview]
Message-ID: <30a7a7e3a74b4b169ba47e100be44ee8@huawei.com> (raw)
In-Reply-To: <YuAbm09hv4ZGXIw5@kroah.com>

Thanks for your advice, I will delete the log and send a new patch. 

-----邮件原件-----
发件人: Greg KH <gregkh@linuxfoundation.org> 
发送时间: 2022年7月27日 0:52
收件人: chenxingdi <chenxingdi@huawei.com>
抄送: mathias.nyman@intel.com; linux-usb@vger.kernel.org; linux-kernel@vger.kernel.org; chunkeey@googlemail.com
主题: Re: [PATCH -next] usb: renesas-xhci: Use pr_info while fw verify success

On Tue, Jul 26, 2022 at 02:05:09PM +0800, Chen Xingdi wrote:
> While fw verify success, it is confused to print an error log which is 
> actually not an error, so use pr_info to print firmware version 
> instead of pr_err.
> 
> Signed-off-by: Chen Xingdi <chenxingdi@huawei.com>
> ---
>  drivers/usb/host/xhci-pci-renesas.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/usb/host/xhci-pci-renesas.c 
> b/drivers/usb/host/xhci-pci-renesas.c
> index 52599d96634f..1eb1d863d545 100644
> --- a/drivers/usb/host/xhci-pci-renesas.c
> +++ b/drivers/usb/host/xhci-pci-renesas.c
> @@ -151,7 +151,7 @@ static int renesas_fw_verify(const void *fw_data,
>  	}
>  
>  	fw_version = get_unaligned_le16(fw_data + fw_version_pointer);
> -	pr_err("got firmware version: %02x.", fw_version);
> +	pr_info("got firmware version: %02x.", fw_version);

Why print anything at all?  When drivers are working properly, they should be quiet.  Who relies on this message being sent to the kernel log?

thanks,

greg k-h

  reply	other threads:[~2022-07-27  2:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26  6:05 [PATCH -next] usb: renesas-xhci: Use pr_info while fw verify success Chen Xingdi
2022-07-26 16:51 ` Greg KH
2022-07-27  2:07   ` chenxingdi [this message]
2022-07-27  3:11 ` [PATCH v2 -next] usb: renesas-xhci: Do not print any log while fw verif success Chen Xingdi

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=30a7a7e3a74b4b169ba47e100be44ee8@huawei.com \
    --to=chenxingdi@huawei.com \
    --cc=chunkeey@googlemail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@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