Linux Input/HID development
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Pan Chuang <panchuang@vivo.com>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <bentiss@kernel.org>,
	Zhang Lixu <lixu.zhang@intel.com>,
	Vineeth Pillai <vineeth@bitbyteword.org>,
	"open list:INTEL INTEGRATED SENSOR HUB DRIVER"
	<linux-input@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/4] HID: intel-ish-hid: ipc: Remove redundant dev_err()
Date: Mon, 13 Jul 2026 19:08:16 +0300	[thread overview]
Message-ID: <alUNcCTsTCctMNi2@ashevche-desk.local> (raw)
In-Reply-To: <20260713132439.380121-4-panchuang@vivo.com>

On Mon, Jul 13, 2026 at 09:24:32PM +0800, Pan Chuang wrote:
> Since commit 55b48e23f5c4 ("genirq/devres: Add error handling in
> devm_request_*_irq()"), devm_request_irq() automatically logs
> detailed error messages on failure. Remove the now-redundant
> driver-specific dev_err() calls.

Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2026-07-13 16:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13 13:24 [PATCH 0/4] HID: Remove redundant error messages on IRQ request failure Pan Chuang
2026-07-13 13:24 ` [PATCH 1/4] HID: amd_sfh: Remove redundant dev_err() Pan Chuang
2026-07-13 13:34   ` sashiko-bot
2026-07-13 13:24 ` [PATCH 2/4] HID: hid-goodix: " Pan Chuang
2026-07-13 13:24 ` [PATCH 3/4] HID: intel-ish-hid: ipc: " Pan Chuang
2026-07-13 13:43   ` sashiko-bot
2026-07-13 15:27   ` srinivas pandruvada
2026-07-13 16:08   ` Andy Shevchenko [this message]
2026-07-13 13:24 ` [PATCH 4/4] HID: Intel-thc-hid: Intel-quickspi: " Pan Chuang
2026-07-13 13:35   ` sashiko-bot
2026-07-14  0:50   ` Xu, Even

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=alUNcCTsTCctMNi2@ashevche-desk.local \
    --to=andriy.shevchenko@intel.com \
    --cc=bentiss@kernel.org \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lixu.zhang@intel.com \
    --cc=panchuang@vivo.com \
    --cc=srinivas.pandruvada@linux.intel.com \
    --cc=vineeth@bitbyteword.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