From: Jernej Skrabec <jernej.skrabec@gmail.com>
To: linus.walleij@linaro.org
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Jernej Skrabec <jernej.skrabec@gmail.com>
Subject: [PATCH v2 0/2] pinctrl: pinmux: Update error reporting in pin_request()
Date: Sat, 9 Sep 2023 16:34:55 +0200 [thread overview]
Message-ID: <20230909143457.9149-1-jernej.skrabec@gmail.com> (raw)
Currently pin_request() may prints two error messages for same error.
Additionally, it also prints error message when status is -EPROBE_DEFER.
Fix that by removing duplicate error reporting and use dev_err_probe()
instead of ordinary dev_err().
Best regards,
Jernej
Changes from v1:
- fixed dev_err_probe() arguments
Jernej Skrabec (2):
pinctrl: pinmux: Remove duplicate error message in pin_request()
pinctrl: pinmux: Use dev_err_probe() in pin_request()
drivers/pinctrl/pinmux.c | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
--
2.42.0
next reply other threads:[~2023-09-09 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 14:34 Jernej Skrabec [this message]
2023-09-09 14:34 ` [PATCH v2 1/2] pinctrl: pinmux: Remove duplicate error message in pin_request() Jernej Skrabec
2023-09-09 14:34 ` [PATCH v2 2/2] pinctrl: pinmux: Use dev_err_probe() " Jernej Skrabec
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=20230909143457.9149-1-jernej.skrabec@gmail.com \
--to=jernej.skrabec@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).