From: Philipp Stanner <pstanner@redhat.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
pstanner@redhat.com
Subject: Re: [PATCH v1 1/2] devres: Switch to use dev_err_probe() for unification
Date: Thu, 29 Feb 2024 09:52:34 +0100 [thread overview]
Message-ID: <e2f49a1f1877550c4ca733bbca26949836d4fef1.camel@redhat.com> (raw)
In-Reply-To: <20240227175910.3031342-2-andriy.shevchenko@linux.intel.com>
On Tue, 2024-02-27 at 19:58 +0200, Andy Shevchenko wrote:
> The devm_*() APIs are supposed to be called during the ->probe()
> stage.
> Many drivers (especially new ones) has switched to use
has -> have
> dev_err_probe()
> for error messaging for the sake of unification. Let's do the same in
> the devres APIs.
No objections on principle. Just one thing about the implementation:
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> lib/devres.c | 17 +++++++++--------
> 1 file changed, 9 insertions(+), 8 deletions(-)
>
> diff --git a/lib/devres.c b/lib/devres.c
> index fe0c63caeb68..27f280a39dca 100644
> --- a/lib/devres.c
> +++ b/lib/devres.c
> @@ -125,12 +125,13 @@ __devm_ioremap_resource(struct device *dev,
> const struct resource *res,
> resource_size_t size;
> void __iomem *dest_ptr;
> char *pretty_name;
> + int ret;
>
> BUG_ON(!dev);
>
> if (!res || resource_type(res) != IORESOURCE_MEM) {
> - dev_err(dev, "invalid resource %pR\n", res);
> - return IOMEM_ERR_PTR(-EINVAL);
> + ret = dev_err_probe(dev, -EINVAL, "invalid resource
> %pR\n", res);
> + return IOMEM_ERR_PTR(ret);
So as I see it -EINVAL is just piped through dev_err_probe() and is
never changed.
Don't you think it would be better to drop variable 'ret' and just do
return IOMEM_ERR_PTR(-EINVAL);
as before?
That way it would be obvious that the error code is never changed and
it will always return -EINVAL. Otherwise you have to look up the
function definition of dev_err_probe().
The same would apply below.
Regards,
P.
> }
>
> if (type == DEVM_IOREMAP && res->flags &
> IORESOURCE_MEM_NONPOSTED)
> @@ -144,20 +145,20 @@ __devm_ioremap_resource(struct device *dev,
> const struct resource *res,
> else
> pretty_name = devm_kstrdup(dev, dev_name(dev),
> GFP_KERNEL);
> if (!pretty_name) {
> - dev_err(dev, "can't generate pretty name for resource
> %pR\n", res);
> - return IOMEM_ERR_PTR(-ENOMEM);
> + ret = dev_err_probe(dev, -ENOMEM, "can't generate
> pretty name for resource %pR\n", res);
> + return IOMEM_ERR_PTR(ret);
> }
>
> if (!devm_request_mem_region(dev, res->start, size,
> pretty_name)) {
> - dev_err(dev, "can't request region for resource
> %pR\n", res);
> - return IOMEM_ERR_PTR(-EBUSY);
> + ret = dev_err_probe(dev, -EBUSY, "can't request
> region for resource %pR\n", res);
> + return IOMEM_ERR_PTR(ret);
> }
>
> dest_ptr = __devm_ioremap(dev, res->start, size, type);
> if (!dest_ptr) {
> - dev_err(dev, "ioremap failed for resource %pR\n",
> res);
> devm_release_mem_region(dev, res->start, size);
> - dest_ptr = IOMEM_ERR_PTR(-ENOMEM);
> + ret = dev_err_probe(dev, -ENOMEM, "ioremap failed for
> resource %pR\n", res);
> + return IOMEM_ERR_PTR(ret);
> }
>
> return dest_ptr;
next prev parent reply other threads:[~2024-02-29 8:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 17:58 [PATCH v1 0/2] devres: A couple of cleanups Andy Shevchenko
2024-02-27 17:58 ` [PATCH v1 1/2] devres: Switch to use dev_err_probe() for unification Andy Shevchenko
2024-02-29 8:52 ` Philipp Stanner [this message]
2024-02-29 10:39 ` Andy Shevchenko
2024-02-29 10:41 ` Andy Shevchenko
2024-02-27 17:58 ` [PATCH v1 2/2] devres: Don't use "proxy" headers 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=e2f49a1f1877550c4ca733bbca26949836d4fef1.camel@redhat.com \
--to=pstanner@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
/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®