From: Dan Carpenter <error27@gmail.com>
To: Melih Emik <melihemik@noirlang.tr>
Cc: parthiban.veerasooran@microchip.com,
christian.gromm@microchip.com, gregkh@linuxfoundation.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: most: dim2: remove redundant dev_err() calls
Date: Sun, 18 Oct 2026 13:45:27 +0300 [thread overview]
Message-ID: <atSjRzJ3_ORJ_uh9@stanley.mountain> (raw)
In-Reply-To: <20261018104223.164776-1-melihemik@noirlang.tr>
On Sun, Oct 18, 2026 at 01:42:23PM +0300, Melih Emik wrote:
> Since commit 55b48e23f5c4 ("genirq/devres: Add error handling in
> devm_request_*_irq()"), devm_request_threaded_irq() and
> devm_request_irq() automatically log detailed failure diagnostics
> including device name, IRQ number, handlers, and the error code via
> dev_err_probe().
>
> Consequently, driver-specific dev_err() calls immediately following
> these requests produce duplicate error messages on failure and are
> redundant. Remove the redundant dev_err() calls in dim2_probe().
>
> Tested:
> - Compiled with W=1 on x86_64 with zero warnings.
> - Verified with lockdep and debug mutexes enabled
> (CONFIG_PROVE_LOCKING=y, CONFIG_DEBUG_MUTEXES=y).
> - Boot-tested full bzImage in QEMU with initcall_debug, confirming
> successful driver registration (dim2_driver_init returned 0) and
> zero lockdep/kernel warnings.
> - Verified with scripts/checkpatch.pl (0 errors, 0 warnings).
Don't put this kind of meta commentary in the commit message. It's
expected that people test their patches, so there is no need to say
it. If there is something unexpected then put it below the ---
cut off line
>
> Signed-off-by: Melih Emik <melihemik@noirlang.tr>
> ---
^^^
here.
regards,
dan carpenter
next prev parent reply other threads:[~2026-10-18 10:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 10:42 [PATCH] staging: most: dim2: remove redundant dev_err() calls Melih Emik
2026-10-18 10:45 ` Dan Carpenter [this message]
2026-10-18 11:00 ` Melih Emik
2026-10-18 11:06 ` Dan Carpenter
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=atSjRzJ3_ORJ_uh9@stanley.mountain \
--to=error27@gmail.com \
--cc=christian.gromm@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=melihemik@noirlang.tr \
--cc=parthiban.veerasooran@microchip.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.