mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Bui Duc Phuc <phucduc.bui@gmail.com>
Cc: <linux-sound@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	"Sylwester Nawrocki" <s.nawrocki@samsung.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	"Mark Brown" <broonie@kernel.org>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH 2/6] ASoC: samsung: aries_wm8994: Drop redundant probe error messages
Date: Wed, 12 Aug 2026 08:52:44 +0200	[thread overview]
Message-ID: <4b311faf-6269-4904-9658-9ef6f6b0114d@intel.com> (raw)
In-Reply-To: <CAABR9nGxPv+XUmaRBUoS=sU3vaUdfRT533NyqZFq5fGkTzz30w@mail.gmail.com>

On 8/12/2026 4:59 AM, Bui Duc Phuc wrote:

>> To be fair, xxx_snd_soc_register_component(), both the devres and the
>> non-devres equivalent do not report anything.  The
>> component_initialize() and component_add() do though, most of the time.
>>
> 
> Yes, you're right. I checked and all the error paths before returning already
> log an error, except for -ENOMEM, which by convention doesn't need to be logged.
> 
> I'll update the commit message to clarify that the error is logged deeper in
> the call chain rather than by the function called directly. Something like:
> 
> -------
> The functions called here don't log the error themselves, but the
> error is already reported deeper in the call chain, so the dev_err()
> calls are redundant and can be removed.
> -------
> Does this look accurate to you?
Looks good.

  reply	other threads:[~2026-08-12  6:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11  9:05 [PATCH 0/6] ASoC: samsung: Improve probe error handling phucduc.bui
2026-08-11  9:05 ` [PATCH 1/6] ASoC: samsung: aries_wm8994: Preserve gpiod_to_irq() error codes phucduc.bui
2026-08-11 13:17   ` Cezary Rojewski
2026-08-11  9:05 ` [PATCH 2/6] ASoC: samsung: aries_wm8994: Drop redundant probe error messages phucduc.bui
2026-08-11 13:10   ` Cezary Rojewski
2026-08-12  2:59     ` Bui Duc Phuc
2026-08-12  6:52       ` Cezary Rojewski [this message]
2026-08-11  9:05 ` [PATCH 3/6] ASoC: samsung: pcm: Use dev_err_probe() for error handling phucduc.bui
2026-08-11 13:21   ` Cezary Rojewski
2026-08-11  9:05 ` [PATCH 4/6] ASoC: samsung: pcm: Drop redundant probe error messages phucduc.bui
2026-08-11  9:05 ` [PATCH 5/6] ASoC: samsung: spdif: " phucduc.bui
2026-08-11 13:16   ` Cezary Rojewski
2026-08-11  9:05 ` [PATCH 6/6] ASoC: samsung: tm2_wm5110: " phucduc.bui

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=4b311faf-6269-4904-9658-9ef6f6b0114d@intel.com \
    --to=cezary.rojewski@intel.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=phucduc.bui@gmail.com \
    --cc=s.nawrocki@samsung.com \
    --cc=tiwai@suse.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

all inboxes | Powered by JetHome®