public inbox for linux-fbdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Artem Lytkin <iprintercanon@gmail.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
	Teddy Wang <teddy.wang@siliconmotion.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org,
	Artem Lytkin <iprintercanon@gmail.com>
Subject: [PATCH v4 0/3] staging: sm750fb: clean up logging
Date: Sat,  7 Feb 2026 15:37:00 +0000	[thread overview]
Message-ID: <20260207153703.2049-1-iprintercanon@gmail.com> (raw)

This series cleans up the logging in the sm750fb driver.

Changes since v3:
  - Dropped the strcat and strncmp patches as requested by Greg KH
  - Consistently removed all pr_info/pr_debug/pr_warn diagnostic prints
    in one patch (previously some fb_find_mode prints were kept)
  - Split dev_err conversions into two patches: one for sm750.c
    and one for sm750_hw.c

Patch 1 removes all pr_info/pr_debug/pr_warn diagnostic prints
from both sm750.c and sm750_hw.c. These include address dumps,
debug variable prints, fb_find_mode result logging, and CH7301
DVI chip status messages.

Patches 2-3 convert the remaining pr_err() calls to dev_err()
for proper device context.

Artem Lytkin (3):
  staging: sm750fb: remove debug and diagnostic prints
  staging: sm750fb: convert logging to device-based in sm750.c
  staging: sm750fb: convert logging to device-based in sm750_hw.c

 drivers/staging/sm750fb/sm750.c    | 88 +++---------------------------
 drivers/staging/sm750fb/sm750_hw.c | 26 ++-------
 2 files changed, 14 insertions(+), 100 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-02-07 15:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-07 15:37 Artem Lytkin [this message]
2026-02-07 15:37 ` [PATCH v4 1/3] staging: sm750fb: remove debug and diagnostic prints Artem Lytkin
2026-02-07 15:37 ` [PATCH v4 2/3] staging: sm750fb: convert logging to device-based in sm750.c Artem Lytkin
2026-02-07 15:37 ` [PATCH v4 3/3] staging: sm750fb: convert logging to device-based in sm750_hw.c Artem Lytkin
2026-02-23 14:36 ` [PATCH v4 0/3] staging: sm750fb: clean up logging Greg Kroah-Hartman

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=20260207153703.2049-1-iprintercanon@gmail.com \
    --to=iprintercanon@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=teddy.wang@siliconmotion.com \
    /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