From: Krzysztof Kozlowski <krzk@kernel.org>
To: Piotr Kubik <piotr.kubik@adtran.com>,
Oleksij Rempel <o.rempel@pengutronix.de>,
Kory Maincent <kory.maincent@bootlin.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [EXTERNAL]Re: [PATCH net-next 2/2] net: pse-pd: Add Si3474 PSE controller driver
Date: Fri, 16 May 2025 15:30:48 +0200 [thread overview]
Message-ID: <acc244a7-54e8-49d0-848e-6eafb850c93b@kernel.org> (raw)
In-Reply-To: <c23d2b2e-6ebb-4a44-bd23-5a66b2cb4e38@adtran.com>
On 15/05/2025 17:58, Piotr Kubik wrote:
> On 5/15/25 17:40, Krzysztof Kozlowski wrote:
>> On 15/05/2025 17:20, Piotr Kubik wrote:
>>> Thanks Krzysztof for your review,
>>>
>>>> On 13/05/2025 00:06, Piotr Kubik wrote:
>>>>> +/* Parse pse-pis subnode into chan array of si3474_priv */
>>>>> +static int si3474_get_of_channels(struct si3474_priv *priv)
>>>>> +{
>>>>> + struct device_node *pse_node, *node;
>>>>> + struct pse_pi *pi;
>>>>> + u32 pi_no, chan_id;
>>>>> + s8 pairset_cnt;
>>>>> + s32 ret = 0;
>>>>> +
>>>>> + pse_node = of_get_child_by_name(priv->np, "pse-pis");
>>>>> + if (!pse_node) {
>>>>> + dev_warn(&priv->client[0]->dev,
>>>>> + "Unable to parse DT PSE power interface matrix, no pse-pis node\n");
>>>>> + return -EINVAL;
>>>>> + }
>>>>> +
>>>>> + for_each_child_of_node(pse_node, node) {
>>>>
>>>> Use scoped variant. One cleanup less.
>>>
>>> good point
>>>
>>>>
>>>>
>>>>> + if (!of_node_name_eq(node, "pse-pi"))
>>>>> + continue;
>>>>
>>>> ...
>>>>
>>>>> +
>>>>> + ret = i2c_smbus_read_byte_data(client, FIRMWARE_REVISION_REG);
>>>>> + if (ret < 0)
>>>>> + return ret;
>>>>> + fw_version = ret;
>>>>> +
>>>>> + ret = i2c_smbus_read_byte_data(client, CHIP_REVISION_REG);
>>>>> + if (ret < 0)
>>>>> + return ret;
>>>>> +
>>>>> + dev_info(dev, "Chip revision: 0x%x, firmware version: 0x%x\n",
>>>>
>>>> dev_dbg or just drop. Drivers should be silent on success.
>>>
>>> Is there any rule for this I'm not aware of?
>>> I'd like to know that device is present and what versions it runs just by looking into dmesg.
>>> This approach is similar to other drivers, all current PSE drivers log it this way.
>>>
>> And now I noticed that you already sent it, you got review:
>> https://lore.kernel.org/all/6ee047d4-f3de-4c25-aaae-721221dc3003@kernel.org/
>>
>> and you ignored it completely sending the same again.
>>
>> Sending the same over and over and asking us to do the same review over
>> and over is really waste of our time.
>>
>> Go back to v1, implement entire review. Then start versioning your patches.
>>
>> Best regards,
>> Krzysztof
>
>
> I didn't ignore, I replied to your comment, since there was no answer I assumed you agree.
> https://lore.kernel.org/all/38b02e2d-7935-4a23-b351-d23941e781b0@adtran.com/
>
> Thanks for a reference and explanation, I'll change it.
Coding style has it pretty explicit as well.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-05-16 13:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 22:02 [PATCH net-next 0/2] " Piotr Kubik
2025-05-12 22:05 ` [PATCH net-next 1/2] dt-bindings: net: pse-pd: Add bindings for Si3474 PSE controller Piotr Kubik
2025-05-13 8:24 ` Krzysztof Kozlowski
2025-05-15 15:20 ` [EXTERNAL]Re: " Piotr Kubik
2025-05-16 13:37 ` Krzysztof Kozlowski
2025-05-16 14:09 ` Piotr Kubik
2025-05-16 22:35 ` [EXTERNAL]Re: " Kory Maincent
2025-05-17 9:44 ` Piotr Kubik
2025-05-12 22:06 ` [PATCH net-next 2/2] net: pse-pd: Add Si3474 PSE controller driver Piotr Kubik
2025-05-13 8:08 ` Krzysztof Kozlowski
2025-05-15 15:20 ` [EXTERNAL]Re: " Piotr Kubik
2025-05-15 15:32 ` Krzysztof Kozlowski
2025-05-15 15:35 ` Krzysztof Kozlowski
2025-05-15 15:40 ` Krzysztof Kozlowski
2025-05-15 15:58 ` Piotr Kubik
2025-05-16 13:30 ` Krzysztof Kozlowski [this message]
2025-05-13 11:48 ` [PATCH net-next 0/2] " Kory Maincent
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=acc244a7-54e8-49d0-848e-6eafb850c93b@kernel.org \
--to=krzk@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=kory.maincent@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=piotr.kubik@adtran.com \
--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
all inboxes | Powered by JetHome®