From: Krzysztof Kozlowski <krzk@kernel.org>
To: Gary Yang <gary.yang@cixtech.com>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
cix-kernel-upstream <cix-kernel-upstream@cixtech.com>
Subject: Re: 回复: 回复: 回复: 回复: [PATCH 1/3] pinctrl: cix: Add pin-controller support for sky1
Date: Fri, 29 Aug 2025 12:35:50 +0200 [thread overview]
Message-ID: <4879398b-a24c-4ec6-8bb0-90d2c1db2dc8@kernel.org> (raw)
In-Reply-To: <PUZPR06MB588786D49A7C1964E4A39851EF3AA@PUZPR06MB5887.apcprd06.prod.outlook.com>
On 29/08/2025 12:18, Gary Yang wrote:
>>>
>>> So you see the twice, once per one pin-controller. BTW as you suggested
>> before, we will print the value of ret in the error message.
>>>
>>> If I miss any information, please kindly remind me. Thanks
>>
>> You still ignored my second comment.
^^^ That was second time here I reminded about ENOMEM comment.
>>
>
> First you wrote " You are printing same error twice ", please pay attention to the "same error" strings, it makes me confuse, I misunderstand your thinking
> until you took the example above. So the discussion is needed, not waste our time.
>
> Second the return value of sky1_pinctrl_probe_dt() is not only ENOMEM, it can also return ENODEV and EINVAL. Although I don't think this is a bug, take our
The problem is that you ignored the ENOMEM comment and it clearly should
direct you to the problem and solution ("If I cannot have error on
ENOMEM, I will move my error msgs to the called function").
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-29 10:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 2:42 [PATCH 0/3] Add pinctrl support for Sky1 Gary Yang
2025-08-27 2:42 ` [PATCH 1/3] pinctrl: cix: Add pin-controller support for sky1 Gary Yang
2025-08-27 9:07 ` Krzysztof Kozlowski
2025-08-28 6:44 ` 回复: " Gary Yang
2025-08-28 6:49 ` Krzysztof Kozlowski
2025-08-28 8:32 ` 回复: " Gary Yang
2025-08-28 18:00 ` Krzysztof Kozlowski
2025-08-29 4:33 ` 回复: " Gary Yang
2025-08-29 6:21 ` Krzysztof Kozlowski
2025-08-29 10:18 ` 回复: " Gary Yang
2025-08-29 10:35 ` Krzysztof Kozlowski [this message]
2025-08-28 17:51 ` Linus Walleij
2025-08-28 18:02 ` Krzysztof Kozlowski
2025-08-28 21:03 ` Linus Walleij
2025-08-27 2:42 ` [PATCH 2/3] dt-bindings: pinctrl: Add cix,sky1-pinctrl Gary Yang
2025-08-27 8:22 ` Krzysztof Kozlowski
2025-08-28 5:37 ` 回复: " Gary Yang
2025-08-28 6:52 ` Krzysztof Kozlowski
2025-08-28 8:58 ` 回复: " Gary Yang
2025-08-28 18:04 ` Krzysztof Kozlowski
2025-08-28 18:19 ` Linus Walleij
2025-08-30 13:20 ` Gary Yang
2025-09-01 12:55 ` Linus Walleij
2025-09-02 2:08 ` 回复: " Gary Yang
2025-08-28 7:25 ` Krzysztof Kozlowski
2025-08-28 18:27 ` Linus Walleij
2025-08-27 2:42 ` [PATCH 3/3] arm64: dts: cix: Add pinctrl nodes for sky1 Gary Yang
2025-08-27 8:23 ` Krzysztof Kozlowski
2025-08-28 6:14 ` 回复: " Gary Yang
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=4879398b-a24c-4ec6-8bb0-90d2c1db2dc8@kernel.org \
--to=krzk@kernel.org \
--cc=cix-kernel-upstream@cixtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gary.yang@cixtech.com \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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).