Linux Input/HID development
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Bui Duc Phuc <phucduc.bui@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] Input: st-keyscan: Improve probe error handling
Date: Fri, 24 Jul 2026 18:48:06 -0700	[thread overview]
Message-ID: <amQVsmuy3cgm-i5M@google.com> (raw)
In-Reply-To: <CAABR9nGCv3J0cZCb8MYVYXby6HZhoMbpfKdsNeTxFJS3dzuNwA@mail.gmail.com>

On Tue, Jul 21, 2026 at 09:20:30AM +0700, Bui Duc Phuc wrote:
> Hi Dmitry,
> 
> Thank you for your feedback.
> 
> > > Use dev_err_probe() for devm_clk_get() so deferred probe errors are
> > > handled correctly.
> >
> > Same here: in what way the does existing code handle deferred probe
> > incorrectly?
> >
> This is the same case as the previous patch. The current code uses dev_err(),
> which logs an error message even when devm_clk_get() returns -EPROBE_DEFER.
> Since the probe will be retried later, this leads to unnecessary log spam.
> Link to previous discussion for reference:
> https://lore.kernel.org/all/CAABR9nHHe1AzWmqhV0d5p87qfSsBk2O7bYj-Weowyr=99wtNNA@mail.gmail.com/
> 
> Would you like me to send a v3 updating the commit message to be clearer,
> such as: "Use dev_err_probe() for devm_clk_get() to prevent log spam
> when probe returns -EPROBE_DEFER.""
> or keep the current patch as is?

Yes, please, since the handling of deferrals was not broken. We just had
some harmless extra logging.

Thanks.

-- 
Dmitry

  parent reply	other threads:[~2026-07-25  1:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20  9:08 [PATCH v2 1/2] Input: snvs_pwrkey: Improve probe error handling phucduc.bui
2026-07-20  9:08 ` [PATCH v2 2/2] Input: st-keyscan: " phucduc.bui
2026-07-20  9:17   ` sashiko-bot
2026-07-20 17:08   ` Dmitry Torokhov
2026-07-21  2:20     ` Bui Duc Phuc
2026-07-21  2:41       ` Bui Duc Phuc
2026-07-25  1:48       ` Dmitry Torokhov [this message]
2026-07-27  6:43         ` Bui Duc Phuc
2026-07-20 17:07 ` [PATCH v2 1/2] Input: snvs_pwrkey: " Dmitry Torokhov
2026-07-21  1:59   ` Bui Duc Phuc
  -- strict thread matches above, loose matches on Subject: below --
2026-07-27 10:11 phucduc.bui
2026-07-27 10:11 ` [PATCH v2 2/2] Input: st-keyscan: " phucduc.bui
2026-07-27 10:20   ` sashiko-bot

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=amQVsmuy3cgm-i5M@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phucduc.bui@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