From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Shevchenko <andy@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v1 0/4] pinctrl: intel: Unify error messages
Date: Tue, 4 Nov 2025 06:25:39 +0100 [thread overview]
Message-ID: <20251104052539.GK2912318@black.igk.intel.com> (raw)
In-Reply-To: <20251103200235.712436-1-andriy.shevchenko@linux.intel.com>
On Mon, Nov 03, 2025 at 08:58:27PM +0100, Andy Shevchenko wrote:
> Unify error messages with help of dev_err_probe(). This brings
> a common pattern with error code printed as well. While at it,
> make the text message the same for the same reasons across
> the Intel pin control drivers.
>
> Andy Shevchenko (4):
> pinctrl: baytrail: Unify messages with help of dev_err_probe()
> pinctrl: cherryview: Unify messages with help of dev_err_probe()
> pinctrl: intel: Unify messages with help of dev_err_probe()
> pinctrl: tangier: Unify messages with help of dev_err_probe()
For the series,
Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
next prev parent reply other threads:[~2025-11-04 5:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 19:58 [PATCH v1 0/4] pinctrl: intel: Unify error messages Andy Shevchenko
2025-11-03 19:58 ` [PATCH v1 1/4] pinctrl: baytrail: Unify messages with help of dev_err_probe() Andy Shevchenko
2025-11-03 19:58 ` [PATCH v1 2/4] pinctrl: cherryview: " Andy Shevchenko
2025-11-03 19:58 ` [PATCH v1 3/4] pinctrl: intel: " Andy Shevchenko
2025-11-03 19:58 ` [PATCH v1 4/4] pinctrl: tangier: " Andy Shevchenko
2025-11-04 5:25 ` Mika Westerberg [this message]
2025-11-04 8:31 ` [PATCH v1 0/4] pinctrl: intel: Unify error messages 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=20251104052539.GK2912318@black.igk.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy@kernel.org \
--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