Linux LED subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: phucduc.bui@gmail.com, linux-leds@vger.kernel.org
Cc: lee@kernel.org
Subject: Re: [PATCH v3 2/2] leds: lm3532: Avoid duplicate error messages
Date: Wed, 21 Oct 2026 05:01:59 +0000	[thread overview]
Message-ID: <sashiko-outbox-179797@kernel.org> (raw)
In-Reply-To: <20261021045832.16356-2-phucduc.bui@gmail.com>

> From: bui duc phuc <phucduc.bui@gmail.com>
> 
> Most error paths in lm3532_parse_node() already log errors. Remove
> the redundant error message from lm3532_probe() to avoid duplicate
> logs.
> 
> Signed-off-by: bui duc phuc <phucduc.bui@gmail.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261021045832.16356-1-phucduc.bui@gmail.com?part=2


  reply	other threads:[~2026-10-21  5:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21  4:58 [PATCH v3 1/2] leds: lm3532: Propagate enable GPIO errors phucduc.bui
2026-10-21  4:58 ` [PATCH v3 2/2] leds: lm3532: Avoid duplicate error messages phucduc.bui
2026-10-21  5:01   ` sashiko-bot [this message]
2026-10-21  5:01 ` [PATCH v3 1/2] leds: lm3532: Propagate enable GPIO errors 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=sashiko-outbox-179797@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=phucduc.bui@gmail.com \
    --cc=sashiko-reviews@lists.linux.dev \
    /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