From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Cristian Marussi <cristian.marussi@arm.com>
Cc: Sudeep Holla <sudeep.holla@arm.com>, Peng Fan <peng.fan@nxp.com>,
Linus Walleij <linus.walleij@linaro.org>,
"Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
"brgl@bgdev.pl" <brgl@bgdev.pl>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pinctrl: pinconf-generic: check error value EOPNOTSUPP
Date: Fri, 5 Apr 2024 19:27:15 +0300 [thread overview]
Message-ID: <ZhAmY8TiWcRslwqI@smile.fi.intel.com> (raw)
In-Reply-To: <ZhAlg0Zu_2uOQMk_@pluto>
On Fri, Apr 05, 2024 at 05:23:31PM +0100, Cristian Marussi wrote:
> On Fri, Apr 05, 2024 at 07:16:56PM +0300, Andy Shevchenko wrote:
...
> Yes, my point was simply to say to fix the retcode of SCMI pinctrl to comply with
> Pinctrl expectations, and definitely NOT to fix and move to ENOTSUPP all the SCMI
> originated errors across all protocols, since it is NOT what is expected in general
> by other susbsystems.
Yes, that's what will work for me, thanks!
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-04-05 16:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 14:10 [PATCH] pinctrl: pinconf-generic: check error value EOPNOTSUPP Peng Fan (OSS)
2024-04-04 11:44 ` Linus Walleij
2024-04-04 17:05 ` Andy Shevchenko
2024-04-04 19:03 ` Linus Walleij
2024-04-04 19:23 ` Andy Shevchenko
2024-04-05 0:26 ` Peng Fan
2024-04-05 2:13 ` Peng Fan
2024-04-05 9:46 ` Sudeep Holla
2024-04-05 15:39 ` Andy Shevchenko
2024-04-05 15:38 ` Andy Shevchenko
2024-04-05 15:47 ` Sudeep Holla
2024-04-05 15:55 ` Andy Shevchenko
2024-04-05 16:07 ` Sudeep Holla
2024-04-05 16:20 ` Andy Shevchenko
2024-04-05 16:06 ` Cristian Marussi
2024-04-05 16:16 ` Andy Shevchenko
2024-04-05 16:23 ` Cristian Marussi
2024-04-05 16:27 ` Andy Shevchenko [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=ZhAmY8TiWcRslwqI@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=brgl@bgdev.pl \
--cc=cristian.marussi@arm.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=sudeep.holla@arm.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