Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Wed, 28 Sep 2022 17:06:45 +0300
From:   Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To:     Matti Vaittinen <mazziesaccount@gmail.com>
Cc:     Jonathan Cameron <jic23@kernel.org>,
        Lars-Peter Clausen <lars@metafoo.de>,
        Rob Herring <robh+dt@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Nikita Yushchenko <nikita.yoush@cogentembedded.com>,
        Cosmin Tanislav <demonsingur@gmail.com>,
        Jagath Jog J <jagathjog1996@gmail.com>,
        linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
        linux-kernel@vger.kernel.org,
        "Mutanen, Mikko" <Mikko.Mutanen@fi.rohmeurope.com>,
        "Haikola, Heikki" <Heikki.Haikola@fi.rohmeurope.com>
Subject: Re: [RFC PATCH 4/5] iio: accel: Support Kionix/ROHM KX022A
 accelerometer
Message-ID: <YzRU9aRNReonSqbg@smile.fi.intel.com>
References: <cover.1663760018.git.mazziesaccount@gmail.com>
 <fe1088cebb0de70bcb99af517004c1816b696825.1663760018.git.mazziesaccount@gmail.com>
 <20220922180339.30138141@jic23-huawei>
 <3eea7954-3faf-3fc9-7507-c318488c5524@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3eea7954-3faf-3fc9-7507-c318488c5524@gmail.com>
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
Precedence: bulk

On Wed, Sep 28, 2022 at 02:14:14PM +0300, Matti Vaittinen wrote:
> On 9/22/22 20:03, Jonathan Cameron wrote:
> > On Wed, 21 Sep 2022 14:45:35 +0300

...

> > > +		dev_err(dev, "no regmap\n");
> > 
> > Use dev_err_probe() for all dev_err() stuff in probe paths.
> > It ends up cleaner and we don't care about the tiny overhead
> > of checking for deferred.
> 
> This one bothers me a bit. It just does not feel correct to pass -EINVAL for
> the dev_err_probe() so the dev_err_probe() can check if -EINVAL !=
> -EPROBE_DEFER. I do understand perfectly well the consistent use of
> dev_err_probe() for all cases where we get an error-code from a function and
> return it - but using dev_err_probe() when we hard-code the return value in
> code calling the dev_err_probe() does not feel like "the right thing to do"
> (tm).
> 
> Eg, I agree that
> return dev_err_probe(dev, ret, "bar");
> is nice even if we know the function that gave us the "ret" never requests
> defer (as that can change some day).
> 
> However, I don't like issuing:
> return dev_err_probe(dev, -EINVAL, "bar");

This case specifically was added into documentation by 7065f92255bb ("driver
core: Clarify that dev_err_probe() is OK even w/out -EPROBE_DEFER").

> Well, please let me know if you think the dev_err_probe() should be used
> even in cases where we hard code the return to something...

And this should be, of course, maintainer's decision.

-- 
With Best Regards,
Andy Shevchenko