From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andrzej Hajda <a.hajda@samsung.com>
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH v1] driver core: Annotate dev_err_probe() with __must_check
Date: Wed, 26 Aug 2020 17:16:15 +0300 [thread overview]
Message-ID: <20200826141615.GN1891694@smile.fi.intel.com> (raw)
In-Reply-To: <1e3708e5-24f2-18e0-40c0-284853171338@samsung.com>
On Wed, Aug 26, 2020 at 01:23:40PM +0200, Andrzej Hajda wrote:
> On 26.08.2020 12:44, Andy Shevchenko wrote:
> > We have got already new users of this API which interpret it differently
> > and miss the opportunity to optimize their code.
> >
> > In order to avoid similar cases in the future, annotate dev_err_probe()
> > with __must_check.
>
>
> There are many cases where __must_check can be annoying, for example:
>
> ret = ...;
>
> if (ret < 0) {
>
> dev_err_probe(...);
>
> goto cleanup;
Can be
ret = dev_err_probe(...);
> }
>
>
> Or (less frequently):
>
> ptr = ...;
>
> if (IS_ERR(ptr)) {
>
> dev_err_probe(...);
>
> return ptr;
...which basically should be something like
return dev_err_probe_ptr(...);
> }
>
>
> Of course in both cases one can add workarounds, but I am not sure what
> is better.
Me neither, but definitely API in current state allows to make code suboptimal.
So, up to Greg and Rafael to decide.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-08-26 14:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200826104505eucas1p2e6ac15abfb6104fdbc4229fc148cbe02@eucas1p2.samsung.com>
2020-08-26 10:44 ` Andy Shevchenko
2020-08-26 11:23 ` Andrzej Hajda
2020-08-26 14:16 ` Andy Shevchenko [this message]
2020-08-26 15:44 ` Joe Perches
2020-08-26 15:55 ` Andy Shevchenko
2020-08-26 16:14 ` Joe Perches
2020-09-09 6:29 ` Krzysztof Kozlowski
2020-09-09 7:02 ` Greg Kroah-Hartman
2020-09-09 7:08 ` Krzysztof Kozlowski
2020-09-09 7:37 ` Greg Kroah-Hartman
2020-09-09 8:46 ` Andy Shevchenko
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=20200826141615.GN1891694@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=a.hajda@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
/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®