From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org, nicolas.ferre@microchip.com,
garsilva@embeddedor.com,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
arvind.yadav.cs@gmail.com,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
andriy.shevchenko@linux.intel.com, bhumirks@gmail.com
Subject: Re: [alsa-devel] [PATCH] ALSA: ac97c: Fix an error handling path in 'atmel_ac97c_probe()'
Date: Thu, 31 Aug 2017 10:31:33 +0000 [thread overview]
Message-ID: <s5h1snsjaey.wl-tiwai@suse.de> (raw)
In-Reply-To: <20170831101903.avhj5tqywpvfsj4u@sirena.org.uk>
On Thu, 31 Aug 2017 12:19:03 +0200,
Mark Brown wrote:
>
> On Thu, Aug 31, 2017 at 10:10:21AM +0200, Alexandre Belloni wrote:
>
> > And here is the fallout of the stupid, brainless "fixing" of issues
> > reported by static analysis tools.
>
> > This clk_prepare_enable will never fail. If it was going to fail, the
> > platform would never boot to a point were it is able to execute that
> > code. It is really annoying to have so much churn for absolutely 0
> > benefit.
>
> It may currently be the case that the SoCs you're looking at happen to
> make this clock essential but that doesn't mean that it's not going to
> be different in some future SoC, nor that we can't have a software bug
> that this will detect. Being consistent with our error checking also
> means that we can spot places where it might practically be a problem
> more easily, it's even easier if the error checking is there first time
> but it's still worth it to go back later.
... yes, but only when it's done correctly.
This is again a typical problem by such a trivial fix patch: the code
looks as if it were trivial and correct, buried in a patch series that
easily leads to the oversight by the maintainer's review.
thanks,
Takashi
next prev parent reply other threads:[~2017-08-31 10:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 4:40 [PATCH] ALSA: ac97c: Fix an error handling path in 'atmel_ac97c_probe()' Christophe JAILLET
2017-08-31 8:10 ` [alsa-devel] " Alexandre Belloni
2017-08-31 8:23 ` Julia Lawall
2017-08-31 9:04 ` Andy Shevchenko
2017-08-31 9:35 ` Alexandre Belloni
2017-08-31 9:38 ` Andy Shevchenko
2017-08-31 9:57 ` Alexandre Belloni
2017-08-31 9:56 ` Alexandre Belloni
2017-08-31 10:13 ` Takashi Iwai
2017-08-31 10:19 ` Alexandre Belloni
2017-08-31 10:23 ` Takashi Iwai
2017-08-31 10:37 ` Mark Brown
2017-08-31 10:49 ` Takashi Iwai
2017-08-31 10:19 ` Mark Brown
2017-08-31 10:31 ` Takashi Iwai [this message]
2017-08-31 10:38 ` Mark Brown
2017-08-31 19:08 ` Christophe JAILLET
2017-08-31 20:50 ` Alexandre Belloni
2017-08-31 21:07 ` Julia Lawall
2017-08-31 11:55 ` Applied "ALSA: ac97c: Fix an error handling path in 'atmel_ac97c_probe()'" to the asoc tree Mark Brown
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=s5h1snsjaey.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alexandre.belloni@free-electrons.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arvind.yadav.cs@gmail.com \
--cc=bhumirks@gmail.com \
--cc=broonie@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=garsilva@embeddedor.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox