linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ladislav Michl <ladis@linux-mips.org>
To: linux-fbdev@vger.kernel.org
Subject: [PATCH v2 0/5] video: udlfb: (not only) Logging cleanup
Date: Thu, 04 Jan 2018 19:36:23 +0000	[thread overview]
Message-ID: <20180104193623.GA22612@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.

Changes in v2:
- Dropped patch "Delete error messages for failed allocations"
- Dropped patch "Remove unnecessary 'return'"
- Added patch "Remove noisy warnings"
- Reordered patches
- Rebased against next-20180104
  Please note as kernel compilation fails with:
    kernel/exit.o: In function `__crc_abort':
    exit.c:(*ABS*+0xc0e2ec8b): multiple definition of `__crc_abort'
    Makefile:1029: recipe for target 'vmlinux' failed
  this patchset is not runtime tested.

Ladislav Michl (5):
  video: udlfb: Remove unnecessary local variable
  video: udlfb: Remove redundant gdev variable
  video: udlfb: Remove noisy warnings
  video: udlfb: Do not name private data 'dev'
  video: udlfb: Switch from the pr_*() to the dev_*() logging functions

 drivers/video/fbdev/udlfb.c | 635 +++++++++++++++++++++-----------------------
 include/video/udlfb.h       |   3 +-
 2 files changed, 302 insertions(+), 336 deletions(-)

-- 
2.15.1


             reply	other threads:[~2018-01-04 19:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04 19:36 Ladislav Michl [this message]
2018-01-08 16:55 ` [PATCH v2 0/5] video: udlfb: (not only) Logging cleanup Ladislav Michl
2018-01-15 14:28 ` Bartlomiej Zolnierkiewicz
2018-01-15 15:30 ` Ladislav Michl
2018-01-15 15:37 ` 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=20180104193623.GA22612@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).