public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Artem Lytkin <iprintercanon@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
	Teddy Wang <teddy.wang@siliconmotion.com>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	Artem Lytkin <iprintercanon@gmail.com>
Subject: [PATCH v5 0/2] staging: sm750fb: clean up logging
Date: Mon, 23 Feb 2026 20:40:34 +0000	[thread overview]
Message-ID: <20260223204036.1780-1-iprintercanon@gmail.com> (raw)

This series cleans up the logging in the sm750fb driver.

Changes since v4:
  - Rebased on staging-testing to resolve conflicts with CamelCase
    renames (fixId, initParm) that landed since v4
  - Dropped patch 2/3 (sm750.c dev_err conversion) as it was already
    applied from v4

Patch 1 removes all pr_info/pr_debug/pr_warn diagnostic prints
from both sm750.c and sm750_hw.c.

Patch 2 converts the remaining pr_err() calls to dev_err() in
sm750_hw.c for proper device context.

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

 drivers/staging/sm750fb/sm750.c    | 76 +-----------------------------
 drivers/staging/sm750fb/sm750_hw.c | 26 ++--------
 2 files changed, 7 insertions(+), 95 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-02-23 20:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23 20:40 Artem Lytkin [this message]
2026-02-23 20:40 ` [PATCH v5 1/2] staging: sm750fb: remove debug and diagnostic prints Artem Lytkin
2026-02-23 20:40 ` [PATCH v5 2/2] staging: sm750fb: convert logging to device-based in sm750_hw.c Artem Lytkin

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=20260223204036.1780-1-iprintercanon@gmail.com \
    --to=iprintercanon@gmail.com \
    --cc=gregkh@linuxfoundation.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