linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Magnus Damm <damm@opensource.se>
Cc: linux-serial@vger.kernel.org, geert+renesas@glider.be,
	gregkh@linuxfoundation.org, linux-renesas-soc@vger.kernel.org,
	jirislaby@kernel.org
Subject: Re: [PATCH] serial: sh-sci: Use dev_dbg() for frame and parity errors
Date: Sat, 4 Dec 2021 16:30:30 +0100	[thread overview]
Message-ID: <YauJlvC7CbCxAhU2@kunai> (raw)
In-Reply-To: <163862557847.23421.1243156045279776895.sendpatchset@octo>

[-- Attachment #1: Type: text/plain, Size: 595 bytes --]

Hi Magnus,

On Sat, Dec 04, 2021 at 10:46:18PM +0900, Magnus Damm wrote:
> From: Magnus Damm <damm+renesas@opensource.se>
> 
> Adjust the console printout handling for frame and parity errors to the same
> style as for break errors by using dev_dbg() instead of dev_notice().
> This reduces the amount of console printouts generated by the defconfig kernel
> on ARM R-Car Gen3 for certain use cases.
> 
> Signed-off-by: Magnus Damm <damm+renesas@opensource.se>

Could we maybe just remove them because there are dedicated counters for
this?

Have a nice weekend,

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-12-04 15:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-04 13:46 [PATCH] serial: sh-sci: Use dev_dbg() for frame and parity errors Magnus Damm
2021-12-04 15:30 ` Wolfram Sang [this message]
2021-12-05  0:45   ` Magnus Damm
2021-12-05  7:16     ` Wolfram Sang

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=YauJlvC7CbCxAhU2@kunai \
    --to=wsa+renesas@sang-engineering.com \
    --cc=damm@opensource.se \
    --cc=geert+renesas@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-serial@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;
as well as URLs for NNTP newsgroup(s).