From: Mike Gerow <gerow@google.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] video: fbdev: udlfb: drop log level for blanking
Date: Thu, 01 Jun 2017 20:38:50 +0000 [thread overview]
Message-ID: <20170601203850.GB10180@google.com> (raw)
In-Reply-To: <20170601202559.GA96809@google.com>
[-- Attachment #1: Type: text/plain, Size: 319 bytes --]
It would also be far simpler (and perhaps better) to just drop the existing log
to debug instead of this conditional nonsense. I'm mostly interested in being
able to check a machine running for a few weeks and seeing the logs not be 95%
"udlfb: /dev/fb1 FB_BLANK mode 0 --> 0".
--
Mike Gerow
gerow@google.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2017-06-01 20:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 20:25 [PATCH] video: fbdev: udlfb: drop log level for blanking Mike Gerow
2017-06-01 20:38 ` Mike Gerow [this message]
2017-06-07 13:33 ` Bartlomiej Zolnierkiewicz
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=20170601203850.GB10180@google.com \
--to=gerow@google.com \
--cc=linux-fbdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.