Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Pan Chuang <panchuang@vivo.com>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Vaibhav Hiremath" <hvaibhav.linux@gmail.com>,
	"Johan Hovold" <johan@kernel.org>,
	"Alex Elder" <elder@kernel.org>, "Nuno Sá" <nuno.sa@analog.com>,
	"Michael Hennerich" <Michael.Hennerich@analog.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Hans de Goede" <hansg@kernel.org>,
	"Mauro Carvalho Chehab" <mchehab@kernel.org>,
	"Sakari Ailus" <sakari.ailus@linux.intel.com>,
	"Parthiban Veerasooran" <parthiban.veerasooran@microchip.com>,
	"Christian Gromm" <christian.gromm@microchip.com>,
	"Marc Dietrich" <marvin24@gmx.de>,
	"Ovidiu Panait" <ovidiu.panait.oss@gmail.com>,
	"Dan Carpenter" <error27@gmail.com>,
	"Gustavo Piaz da Silva" <gustavopiazdasilva2102@gmail.com>,
	"Pan Chuang" <panchuang@vivo.com>,
	"Chelsy Ratnawat" <chelsyratnawat2001@gmail.com>,
	"Gabriel Rondon" <grondon@gmail.com>,
	"Artem Lytkin" <iprintercanon@gmail.com>,
	"Zeeshan Ahmad" <zeeshanahmad022019@gmail.com>,
	"Rajveer Chaudhari" <rajveer.chaudhari.linux@gmail.com>,
	"Ethan Tidmore" <ethantidmore06@gmail.com>,
	"Batu Ada Tutkun" <batuadatutkun@gmail.com>,
	linux-staging@lists.linux.dev (open list:STAGING SUBSYSTEM),
	linux-kernel@vger.kernel.org (open list),
	dri-devel@lists.freedesktop.org (open list:FBTFT Framebuffer
	drivers),
	linux-fbdev@vger.kernel.org (open list:FBTFT Framebuffer drivers),
	greybus-dev@lists.linaro.org (moderated list:GREYBUS SUBSYSTEM),
	linux@analog.com (open list:ANALOG DEVICES INC IIO DRIVERS),
	linux-iio@vger.kernel.org (open list:STAGING - INDUSTRIAL IO),
	linux-media@vger.kernel.org (open list:STAGING - ATOMISP DRIVER),
	ac100@lists.launchpad.net (moderated list:STAGING - NVIDIA
	COMPLIANT EMBEDDED CONTROLLER...),
	linux-tegra@vger.kernel.org (open list:STAGING - NVIDIA
	COMPLIANT EMBEDDED CONTROLLER...)
Subject: [PATCH 0/7] staging: Remove redundant error messages on IRQ request failure
Date: Mon, 20 Jul 2026 21:43:06 +0800	[thread overview]
Message-ID: <20260720134324.239391-1-panchuang@vivo.com> (raw)

devm_request_threaded_irq() and devm_request_any_context_irq()
automatically log detailed error messages on failure via
the devm_request_result() helper, which prints device
name, IRQ number, handler functions, and error code.

Since devm_request_irq() is a static inline wrapper around
devm_request_threaded_irq(), it also benefits from this
automatic logging.

Remove the now-redundant dev_err() and dev_err_probe() calls
in staging drivers that follow these devm_request_*_irq()
functions, as the core now provides more detailed diagnostic
information on failure.

Pan Chuang (7):
  staging: axis-fifo: Remove redundant dev_err()
  staging: fbtft: Remove redundant dev_err_probe()
  staging: greybus: arche-platform: Remove redundant dev_err()
  staging: iio: adt7316: Remove redundant dev_err()
  media: atomisp: Remove redundant dev_err()
  staging: most: dim2: Remove redundant dev_err()
  staging: nvec: Remove redundant dev_err_probe()

 drivers/staging/axis-fifo/axis-fifo.c            | 5 +----
 drivers/staging/fbtft/fb_st7789v.c               | 2 +-
 drivers/staging/greybus/arche-platform.c         | 4 +---
 drivers/staging/iio/addac/adt7316.c              | 5 +----
 drivers/staging/media/atomisp/pci/atomisp_v4l2.c | 4 +---
 drivers/staging/most/dim2/dim2.c                 | 8 ++------
 drivers/staging/nvec/nvec.c                      | 2 +-
 7 files changed, 8 insertions(+), 22 deletions(-)

-- 
2.34.1


             reply	other threads:[~2026-07-20 13:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20 13:43 Pan Chuang [this message]
2026-07-20 13:43 ` [PATCH 2/7] staging: fbtft: Remove redundant dev_err_probe() Pan Chuang
2026-07-20 18:18   ` Andy Shevchenko

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=20260720134324.239391-1-panchuang@vivo.com \
    --to=panchuang@vivo.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=ac100@lists.launchpad.net \
    --cc=andy@kernel.org \
    --cc=batuadatutkun@gmail.com \
    --cc=chelsyratnawat2001@gmail.com \
    --cc=christian.gromm@microchip.com \
    --cc=dlechner@baylibre.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=elder@kernel.org \
    --cc=error27@gmail.com \
    --cc=ethantidmore06@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=greybus-dev@lists.linaro.org \
    --cc=grondon@gmail.com \
    --cc=gustavopiazdasilva2102@gmail.com \
    --cc=hansg@kernel.org \
    --cc=hvaibhav.linux@gmail.com \
    --cc=iprintercanon@gmail.com \
    --cc=jic23@kernel.org \
    --cc=johan@kernel.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux@analog.com \
    --cc=marvin24@gmx.de \
    --cc=mchehab@kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=ovidiu.panait.oss@gmail.com \
    --cc=parthiban.veerasooran@microchip.com \
    --cc=rajveer.chaudhari.linux@gmail.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=zeeshanahmad022019@gmail.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