From: Sean Young <sean@mess.org>
To: Bodo Eggert <7eggert@gmx.de>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] serial_ir: change "ignoring spike" to debug level
Date: Thu, 26 Dec 2019 17:29:37 +0000 [thread overview]
Message-ID: <20191226172937.GB24174@gofer.mess.org> (raw)
In-Reply-To: <20191225180256.4069-1-7eggert@gmx.de>
Hi,
On Wed, Dec 25, 2019 at 07:02:56PM +0100, Bodo Eggert wrote:
> At least on my system with a self-made IR receiver, my kernel log is filled with:
> serial_ir serial_ir.0: ignoring spike: 1 1 1419988034627194ns 1419956080709377ns
>
> These messages happen at random and do not prevent the receiver from
> working. Also I cannot change the features of the IC, therefore they are not
> useful. Probably they are not useful at all.
>
> However they fill the console, they accumulate and fill the dmesg log, by
> doing this, they prevent me from seeing important message.
I think this patch is right, but it needs a Signed-off-by: line.
See:
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin
Thanks,
Sean
> ---
> drivers/media/rc/serial_ir.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/media/rc/serial_ir.c b/drivers/media/rc/serial_ir.c
> index 7652e982173f..d77507ba0fb5 100644
> --- a/drivers/media/rc/serial_ir.c
> +++ b/drivers/media/rc/serial_ir.c
> @@ -353,7 +353,7 @@ static irqreturn_t serial_ir_irq_handler(int i, void *blah)
> dcd = (status & hardware[type].signal_pin) ? 1 : 0;
>
> if (dcd == last_dcd) {
> - dev_err(&serial_ir.pdev->dev,
> + dev_dbg(&serial_ir.pdev->dev,
> "ignoring spike: %d %d %lldns %lldns\n",
> dcd, sense, ktime_to_ns(kt),
> ktime_to_ns(serial_ir.lastkt));
> --
> 2.24.0
next prev parent reply other threads:[~2019-12-26 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-25 18:02 [PATCH] serial_ir: change "ignoring spike" to debug level Bodo Eggert
2019-12-26 17:29 ` Sean Young [this message]
2019-12-26 21:28 ` Bodo Eggert
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=20191226172937.GB24174@gofer.mess.org \
--to=sean@mess.org \
--cc=7eggert@gmx.de \
--cc=linux-media@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