From: Krzysztof Kozlowski <krzk@kernel.org>
To: Yan Zhen <yanzhen@vivo.com>,
ckeepax@opensource.cirrus.com, rf@opensource.cirrus.com,
linus.walleij@linaro.org
Cc: linux-sound@vger.kernel.org, patches@opensource.cirrus.com,
linux-kernel@vger.kernel.org, opensorce.kernel@vivo.com
Subject: Re: [PATCH v3] pinctrl: madera: Simplify with dev_err_probe()
Date: Fri, 30 Aug 2024 19:57:49 +0200 [thread overview]
Message-ID: <71c83616-ea3d-48a4-a722-2fca696a96d1@kernel.org> (raw)
In-Reply-To: <20240830084309.395129-1-yanzhen@vivo.com>
On 30/08/2024 10:43, Yan Zhen wrote:
>
> diff --git a/drivers/pinctrl/cirrus/pinctrl-madera-core.c b/drivers/pinctrl/cirrus/pinctrl-madera-core.c
> index 898b197c3738..2932d7aba725 100644
> --- a/drivers/pinctrl/cirrus/pinctrl-madera-core.c
> +++ b/drivers/pinctrl/cirrus/pinctrl-madera-core.c
> @@ -1063,12 +1063,9 @@ static int madera_pin_probe(struct platform_device *pdev)
> if (pdata->gpio_configs) {
> ret = pinctrl_register_mappings(pdata->gpio_configs,
> pdata->n_gpio_configs);
> - if (ret) {
> - dev_err(priv->dev,
> - "Failed to register pdata mappings (%d)\n",
> - ret);
> - return ret;
> - }
> + if (ret)
> + return dev_err_probe(priv->dev, ret,
> + "Failed to register pdata mappings\n");
Another example, one of many from @vivo.com, where you touch one line
and leave everything else not modified.
Are you going to send 5 different patches - one per each line? You
generate tremendous amount of work for reviewers, just to ramp up your
stats in company.
Best regards,
Krzysztof
prev parent reply other threads:[~2024-08-30 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 8:43 [PATCH v3] pinctrl: madera: Simplify with dev_err_probe() Yan Zhen
2024-08-30 17:57 ` Krzysztof Kozlowski [this message]
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=71c83616-ea3d-48a4-a722-2fca696a96d1@kernel.org \
--to=krzk@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=opensorce.kernel@vivo.com \
--cc=patches@opensource.cirrus.com \
--cc=rf@opensource.cirrus.com \
--cc=yanzhen@vivo.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