From: Ladislav Michl <ladis@linux-mips.org>
To: linux-fbdev@vger.kernel.org
Subject: [PATCH 0/6] video: udlfb: (not only) Logging cleanup
Date: Mon, 11 Dec 2017 21:39:48 +0000 [thread overview]
Message-ID: <20171211213948.GA29173@lenoch> (raw)
This patchset is a side product of debugging on unreliable USB host
where devices saw a lot of disconnects. It turned out that udlfb
logging is just too noisy to be usefull as produced syslog is hard
to read.
Hence this attempt to clean things up.
Comments and suggestions welcome and appreciated, as always.
Ladislav Michl (6):
video: udlfb: Do not name private data 'dev'
video: udlfb: Remove unnecessary 'return'
video: udlfb: Remove unnecessary local variable
video: udlfb: Delete error messages for failed allocations
video: udlfb: Remove redundant gdev variable
video: udlfb: Switch from the pr_*() to the dev_*() logging functions
drivers/video/fbdev/udlfb.c | 617 ++++++++++++++++++++------------------------
include/video/udlfb.h | 3 +-
2 files changed, 284 insertions(+), 336 deletions(-)
next reply other threads:[~2017-12-11 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 21:39 Ladislav Michl [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-04 15:40 [PATCH 0/6] video: udlfb: (not only) Logging cleanup 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=20171211213948.GA29173@lenoch \
--to=ladis@linux-mips.org \
--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 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).