netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Piotr Kubik <piotr.kubik@adtran.com>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
	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 v5 2/2] net: pse-pd: Add Si3474 PSE controller driver
Date: Fri, 18 Jul 2025 18:09:20 +0000	[thread overview]
Message-ID: <01bce50b-77e1-4ee5-8a02-9db7a2845c8f@adtran.com> (raw)
In-Reply-To: <20250718192638.681ef327@kmaincent-XPS-13-7390>

On 7/18/25 19:26, Kory Maincent wrote:
> Le Fri, 11 Jul 2025 11:25:02 +0000,
> Piotr Kubik <piotr.kubik@adtran.com> a écrit :
...
> 
>> +static int si3474_pi_get_admin_state(struct pse_controller_dev *pcdev, int
>> id,
>> +				     struct pse_admin_state *admin_state)
>> +{
>> +	struct si3474_priv *priv = to_si3474_priv(pcdev);
>> +	struct i2c_client *client;
>> +	s32 ret;
>> +	u8 chan0, chan1;
>> +	bool is_enabled = false;
> 
> I think you forgot to fix the xmas style here. 
...>> +
>> +static int si3474_pi_disable(struct pse_controller_dev *pcdev, int id)
>> +{
>> +	struct si3474_priv *priv = to_si3474_priv(pcdev);
>> +	struct i2c_client *client;
>> +	s32 ret;
>> +	u8 chan0, chan1;
>> +	u8 val = 0;
> 
> And here, and other places in the patch. Are you sure you did it as you
> described in your cover letter?
> The code seems ok otherwise.

Well, my bad. I read too quickly and understood netdev rev xmas style description:
"Order the variable declaration lines longest to shortest"
as order the variable declaration by their size, longest to shortest (which I even considered reasonable)

Will fix 

Thanks 
/Piotr

      reply	other threads:[~2025-07-18 18:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-11 11:23 [PATCH net-next v5 0/2] Add Si3474 PSE controller driver Piotr Kubik
2025-07-11 11:24 ` [PATCH net-next v5 1/2] dt-bindings: net: pse-pd: Add bindings for Si3474 PSE controller Piotr Kubik
2025-07-11 11:25 ` [PATCH net-next v5 2/2] net: pse-pd: Add Si3474 PSE controller driver Piotr Kubik
2025-07-16  0:53   ` Jakub Kicinski
2025-07-18 17:14     ` Kory Maincent
2025-07-16 22:22   ` Jakub Kicinski
2025-07-18 17:26   ` Kory Maincent
2025-07-18 18:09     ` Piotr Kubik [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=01bce50b-77e1-4ee5-8a02-9db7a2845c8f@adtran.com \
    --to=piotr.kubik@adtran.com \
    --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=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).